Semi-persistent Scheduling Release

ABSTRACT

A base station transmits RRC message(s) comprising a first configuration parameter of a first SPS configuration, a second configuration parameter of a second SPS configuration, and a third configuration parameter. The first configuration parameter may indicate a first HARQ codebook identifier. The second configuration parameter may indicate a second HARQ codebook identifier. The second HARQ codebook identifier may be the same as the first HARQ codebook identifier. The third configuration parameter may indicate a state that is mapped to the first SPS configuration and the second SPS configuration. A DCI may be transmitted. A value of bit(s) of a HARQ process number field of the DCI may indicate the state. The DCI may indicate deactivation of the first SPS configuration and the second SPS configuration. An acknowledgement may be received.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/385,691, filed Jul. 26, 2021, which is a continuation of U.S.application Ser. No. 17/236,001, filed Apr. 21, 2021, which is acontinuation of U.S. patent application Ser. No. 17/086,383, filed Oct.31, 2020, which claims the benefit of U.S. Provisional Application No.62/931,798, filed Nov. 6, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A and FIG. 1B show examples of mobile communications systems inaccordance with several of various embodiments of the presentdisclosure.

FIG. 2A and FIG. 2B show examples of user plane and control planeprotocol layers in accordance with several of various embodiments of thepresent disclosure.

FIG. 3 shows example functions and services offered by protocol layersin a user plane protocol stack in accordance with several of variousembodiments of the present disclosure.

FIG. 4 shows example flow of packets through the protocol layers inaccordance with several of various embodiments of the presentdisclosure.

FIG. 5A shows example mapping of channels between layers of the protocolstack and different physical signals in downlink in accordance withseveral of various embodiments of the present disclosure.

FIG. 5B shows example mapping of channels between layers of the protocolstack and different physical signals in uplink in accordance withseveral of various embodiments of the present disclosure.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure.

FIG. 7 shows examples of RRC states and RRC state transitions inaccordance with several of various embodiments of the presentdisclosure.

FIG. 8 shows an example time domain transmission structure in NR bygrouping OFDM symbols into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure.

FIG. 10 shows example adaptation and switching of bandwidth parts inaccordance with several of various embodiments of the presentdisclosure.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure.

FIG. 13A shows example time and frequency structure of SSBs and theirassociations with beams in accordance with several of variousembodiments of the present disclosure.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure.

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processesin accordance with several of various embodiments of the presentdisclosure.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure.

FIG. 16 shows an example HARQ feedback codebook determination process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 17 shows an example joint release/deactivation process of DL SPSconfigurations in accordance with an aspect of an embodiment of thepresent disclosure.

FIG. 18 shows an example HARQ feedback codebook determination process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 19 shows an example HARQ feedback codebook determination process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 20 shows an example process in accordance with an aspect of anembodiment of the present disclosure.

FIG. 21 shows an example HARQ feedback codebook determination process inaccordance with an aspect of an embodiment of the present disclosure.

FIG. 22 shows an example acknowledgement process in accordance with anaspect of an embodiment of the present disclosure.

FIG. 23 shows an example acknowledgement process in accordance with anaspect of an embodiment of the present disclosure.

FIG. 24 shows an example acknowledgement process in accordance with anaspect of an embodiment of the present disclosure.

FIG. 25 shows an example acknowledgement process in accordance with anaspect of an embodiment of the present disclosure.

FIG. 26 shows an example wireless device feedback process in accordancewith an aspect of an embodiment of the present disclosure.

FIG. 27 shows an example wireless device feedback process in accordancewith an aspect of an embodiment of the present disclosure.

FIG. 28 shows an example wireless device feedback process in accordancewith an aspect of an embodiment of the present disclosure.

FIG. 29 shows an example wireless device feedback process in accordancewith an aspect of an embodiment of the present disclosure.

FIG. 30 shows an example wireless device feedback process in accordancewith an aspect of an embodiment of the present disclosure.

FIG. 31 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 32 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 33 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 34 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

FIG. 35 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure.

DETAILED DESCRIPTION

The exemplary embodiments of the disclosed technology enablesemi-persistent scheduling operation in a wireless device and/or one ormore base stations. The exemplary disclosed embodiments may beimplemented in the technical field of wireless communication systems.More particularly, the embodiment of the disclosed technology may relateto wireless device feedback for semi-persistent scheduling release.

The devices and/or nodes of the mobile communications system disclosedherein may be implemented based on various technologies and/or variousreleases/versions/amendments of a technology. The various technologiesinclude various releases of long-term evolution (LTE) technologies,various releases of 5G new radio (NR) technologies, various wirelesslocal area networks technologies and/or a combination thereof and/oralike. For example, a base station may support a given technology andmay communicate with wireless devices with different characteristics.The wireless devices may have different categories that define theircapabilities in terms of supporting various features. The wirelessdevice with the same category may have different capabilities. Thewireless devices may support various technologies such as variousreleases of LTE technologies, various releases of 5G NR technologiesand/or a combination thereof and/or alike. At least some of the wirelessdevices in the mobile communications system of the present disclosuremay be stationary or almost stationary. In this disclosure, the terms“mobile communications system” and “wireless communications system” maybe used interchangeably.

FIG. 1A shows an example of a mobile communications system 100 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 100 may be, for example,run by a mobile network operator (MNO) or a mobile virtual networkoperator (MVNO). The mobile communications system 100 may be a publicland mobile network (PLMN) run by a network operator providing a varietyof service including voice, data, short messaging service (SMS),multimedia messaging service (MMS), emergency calls, etc. The mobilecommunications system 100 includes a core network (CN) 106, a radioaccess network (RAN) 104 and at least one wireless device 102.

The CN 106 connects the RAN 104 to one or more external networks (e.g.,one or more data networks such as the Internet) and is responsible forfunctions such as authentication, charging and end-to-end connectionestablishment. Several radio access technologies (RATs) may be served bythe same CN 106.

The RAN 104 may implement a RAT and may operate between the at least onewireless device 102 and the CN 106. The RAN 104 may handle radio relatedfunctionalities such as scheduling, radio resource control, modulationand coding, multi-antenna transmissions and retransmission protocols.The wireless device and the RAN may share a portion of the radiospectrum by separating transmissions from the wireless device to the RANand the transmissions from the RAN to the wireless device. The directionof the transmissions from the wireless device to the RAN is known as theuplink and the direction of the transmissions from the RAN to thewireless device is known as the downlink. The separation of uplink anddownlink transmissions may be achieved by employing a duplexingtechnique. Example duplexing techniques include frequency divisionduplexing (FDD), time division duplexing (TDD) or a combination of FDDand TDD.

In this disclosure, the term wireless device may refer to a device thatcommunicates with a network entity or another device using wirelesscommunication techniques. The wireless device may be a mobile device ora non-mobile (e.g., fixed) device. Examples of the wireless deviceinclude cellular phone, smart phone, tablet, laptop computer, wearabledevice (e.g., smart watch, smart shoe, fitness trackers, smart clothing,etc.), wireless sensor, wireless meter, extended reality (XR) devicesincluding augmented reality (AR) and virtual reality (VR) devices,Internet of Things (IoT) device, vehicle to vehicle communicationsdevice, road-side units (RSU), automobile, relay node or any combinationthereof. In some examples, the wireless device (e.g., a smart phone,tablet, etc.) may have an interface (e.g., a graphical user interface(GUI)) for configuration by an end user. In some examples, the wirelessdevice (e.g., a wireless sensor device, etc.) may not have an interfacefor configuration by an end user. The wireless device may be referred toas a user equipment (UE), a mobile station (MS), a subscriber unit, ahandset, an access terminal, a user terminal, a wireless transmit andreceive unit (WTRU) and/or other terminology.

The at least one wireless device may communicate with at least one basestation in the RAN 104. In this disclosure, the term base station mayencompass terminologies associated with various RATs. For example, abase station may be referred to as a Node B in a 3G cellular system suchas Universal Mobile Telecommunication Systems (UMTS), an evolved Node B(eNB) in a 4G cellular system such as evolved universal terrestrialradio access (E-UTRA), a next generation eNB (ng-eNB), a Next GenerationNode B (gNB) in NR and/or a 5G system, an access point (AP) in Wi-Fiand/or other wireless local area networks. A base station may bereferred to as a remote radio head (RRH), a baseband unit (BBU) inconnection with one or more RRHs, a repeater or relay for coverageextension and/or any combination thereof. In some examples, all protocollayers of a base station may be implemented in one unit. In someexample, some of the protocol layers (e.g., upper layers) of the basestation may be implemented in a first unit (e.g., a central unit (CU))and some other protocol layer (e.g., lower layers) may be implemented inone or more second units (e.g., distributed units (DUs)).

A base station in the RAN 104 includes one or more antennas tocommunicate with the at least one wireless device. The base station maycommunicate with the at least one wireless device using radio frequency(RF) transmissions and receptions via RF transceivers. The base stationantennas may control one or more cells (or sectors). The size and/orradio coverage area of a cell may depend on the range that transmissionsby a wireless device can be successfully received by the base stationwhen the wireless device transmits using the RF frequency of the cell.The base station may be associated with cells of various sizes. At agiven location, the wireless device may be in coverage area of a firstcell of the base station and may not be in coverage area of a secondcell of the base station depending on the sizes of the first cell andthe second cell.

A base station in the RAN 104 may have various implementations. Forexample, a base station may be implemented by connecting a BBU (or a BBUpool) coupled to one or more RRHs and/or one or more relay nodes toextend the cell coverage. The BBU pool may be located at a centralizedsite like a cloud or data center. The BBU pool may be connected to aplurality of RRHs that control a plurality of cells. The combination ofBBU with the one or more RRHs may be referred to as a centralized orcloud RAN (C-RAN) architecture. In some implementations, the BBUfunctions may be implemented on virtual machines (VMs) on servers at acentralized location. This architecture may be referred to as virtualRAN (vRAN). All, most or a portion of the protocol layer functions(e.g., all or portions of physical layer, medium access control (MAC)layer and/or higher layers) may be implemented at the BBU pool and theprocessed data may be transmitted to the RRHs for further processingand/or RF transmission. The links between the BBU pool and the RRHs maybe referred to as fronthaul.

In some deployment scenarios, the RAN 104 may include macrocell basestations with high transmission power levels and large coverage areas.In other deployment scenarios, the RAN 104 may include base stationsthat employ different transmission power levels and/or have cells withdifferent coverage areas. For example, some base station may bemacrocell base stations with high transmission powers and/or largecoverage areas and other base station may be small cell base stationswith comparatively smaller transmission powers and/or coverage areas. Insome deployment scenarios, a small cell base station may have coveragethat is within or has overlap with coverage area of a macrocell basestation. A wireless device may communicate with the macrocell basestation while within the coverage area of the macrocell base station.For additional capacity, the wireless device may communicate with boththe macrocell base station and the small cell base station while in theoverlapped coverage area of the macrocell base station and the smallcell base station. Depending on their coverage areas, a small cell basestation may be referred to as a microcell base station, a picocell basestation, a femtocell base station or a home base station.

Different standard development organizations (SDOs) have specified, ormay specify in future, mobile communications systems that have similarcharacteristics as the mobile communications system 100 of FIG. 1A. Forexample, the Third-Generation Partnership Project (3GPP) is a group ofSDOs that provides specifications that define 3GPP technologies formobile communications systems that are akin to the mobile communicationssystem 100. The 3GPP has developed specifications for third generation(3G) mobile networks, fourth generation (4G) mobile networks and fifthgeneration (5G) mobile networks. The 3G, 4G and 5G networks are alsoknown as Universal Mobile Telecommunications System (UMTS), Long TermEvolution (LTE) and 5G system (5GS), respectively. In this disclosure,embodiments are described with respect to the RAN implemented in a 3GPP5G mobile network that is also referred to as next generation RAN(NG-RAN). The embodiments may also be implemented in other mobilecommunications systems such as 3G or 4G mobile networks or mobilenetworks that may be standardized in future such as sixth generation(6G) mobile networks or mobile networks that are implemented bystandards bodies other than 3GPP. The NG-RAN may be based on a new RATknown as new radio (NR) and/or other radio access technologies such asLTE and/or non-3GPP RATs.

FIG. 1B shows an example of a mobile communications system 110 inaccordance with several of various embodiments of the presentdisclosure. The mobile communications system 110 of FIG. 1B is anexample of a 5G mobile network and includes a 5G CN (5G-CN) 130, anNG-RAN 120 and UEs (collectively 112 and individually UE 112A and UE112B). The 5G-CN 130, the NG-RAN 120 and the UEs 112 of FIG. 1B operatesubstantially alike the CN 106, the RAN 104 and the at least onewireless device 102, respectively, as described for FIG. 1A.

The 5G-CN 130 of FIG. 1B connects the NG-RAN 120 to one or more externalnetworks (e.g., one or more data networks such as the Internet) and isresponsible for functions such as authentication, charging andend-to-end connection establishment. The 5G-CN has new enhancementscompared to previous generations of CNs (e.g., evolved packet core (EPC)in the 4G networks) including service-based architecture, support fornetwork slicing and control plane/user plane split. The service-basedarchitecture of the 5G-CN provides a modular framework based on serviceand functionalities provided by the core network wherein a set ofnetwork functions are connected via service-based interfaces. Thenetwork slicing enables multiplexing of independent logical networks(e.g., network slices) on the same physical network infrastructure. Forexample, a network slice may be for mobile broadband applications withfull mobility support and a different network slice may be fornon-mobile latency-critical applications such as industry automation.The control plane/user plane split enables independent scaling of thecontrol plane and the user plane. For example, the control planecapacity may be increased without affecting the user plane of thenetwork.

The 5G-CN 130 of FIG. 1B includes an access and mobility managementfunction (AMF) 132 and a user plane function (UPF) 134. The AMF 132 maysupport termination of non-access stratum (NAS) signaling, NAS signalingsecurity such as ciphering and integrity protection, inter-3GPP accessnetwork mobility, registration management, connection management,mobility management, access authentication and authorization andsecurity context management. The NAS is a functional layer between a UEand the CN and the access stratum (AS) is a functional layer between theUE and the RAN. The UPF 134 may serve as an interconnect point betweenthe NG-RAN and an external data network. The UPF may support packetrouting and forwarding, packet inspection and Quality of Service (QoS)handling and packet filtering. The UPF may further act as a ProtocolData Unit (PDU) session anchor point for mobility within and betweenRATs.

The 5G-CN 130 may include additional network functions (not shown inFIG. 1B) such as one or more Session Management Functions (SMFs), aPolicy Control Function (PCF), a Network Exposure Function (NEF), aUnified Data Management (UDM), an Application Function (AF), and/or anAuthentication Server Function (AUSF). These network functions alongwith the AMF 132 and UPF 134 enable a service-based architecture for the5G-CN.

The NG-RAN 120 may operate between the UEs 112 and the 5G-CN 130 and mayimplement one or more RATs. The NG-RAN 120 may include one or more gNBs(e.g., gNB 122A or gNB 122B or collectively gNBs 122) and/or one or moreng-eNBs (e.g., ng-eNB 124A or ng-eNB 124B or collectively ng-eNBs 124).The general terminology for gNBs 122 and/or an ng-eNBs 124 is a basestation and may be used interchangeably in this disclosure. The gNBs 122and the ng-eNBs 124 may include one or more antennas to communicate withthe UEs 112. The one or more antennas of the gNBs 122 or ng-eNBs 124 maycontrol one or more cells (or sectors) that provide radio coverage forthe UEs 112.

A gNB and/or an ng-eNB of FIG. 1B may be connected to the 5G-CN 130using an NG interface. A gNB and/or an ng-eNB may be connected withother gNBs and/or ng-eNBs using an Xn interface. The NG or the Xninterfaces are logical connections that may be established using anunderlying transport network. The interface between a UE and a gNB orbetween a UE and an ng-eNBs may be referred to as the Uu interface. Aninterface (e.g., Uu, NG or Xn) may be established by using a protocolstack that enables data and control signaling exchange between entitiesin the mobile communications system of FIG. 1B. When a protocol stack isused for transmission of user data, the protocol stack may be referredto as user plane protocol stack. When a protocol stack is used fortransmission of control signaling, the protocol stack may be referred toas control plane protocol stack. Some protocol layer may be used in bothof the user plane protocol stack and the control plane protocol stackwhile other protocol layers may be specific to the user plane or controlplane.

The NG interface of FIG. 1B may include an NG-User plane (NG-U)interface between a gNB and the UPF 134 (or an ng-eNB and the UPF 134)and an NG-Control plane (NG-C) interface between a gNB and the AMF 132(or an ng-eNB and the AMF 132). The NG-U interface may providenon-guaranteed delivery of user plane PDUs between a gNB and the UPF oran ng-eNB and the UPF. The NG-C interface may provide services such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer and/or warning message transmission.

The UEs 112 and a gNB may be connected using the Uu interface and usingthe NR user plane and control plane protocol stack. The UEs 112 and anng-eNB may be connected using the Uu interface using the LTE user planeand control plane protocol stack.

In the example mobile communications system of FIG. 1B, a 5G-CN isconnected to a RAN comprised of 4G LTE and/or 5G NR RATs. In otherexample mobile communications systems, a RAN based on the 5G NR RAT maybe connected to a 4G CN (e.g., EPC). For example, earlier releases of 5Gstandards may support a non-standalone mode of operation where a NRbased RAN is connected to the 4G EPC. In an example non-standalone mode,a UE may be connected to both a 5G NR gNB and a 4G LTE eNB (e.g., ang-eNB) and the control plane functionalities (such as initial access,paging and mobility) may be provided through the 4G LTE eNB. In astandalone of operation, the 5G NR gNB is connected to a 5G-CN and theuser plane and the control plane functionalities are provided by the 5GNR gNB.

FIG. 2A shows an example of the protocol stack for the user plan of anNR Uu interface in accordance with several of various embodiments of thepresent disclosure. The user plane protocol stack comprises fiveprotocol layers that terminate at the UE 200 and the gNB 210. The fiveprotocol layers, as shown in FIG. 2A, include physical (PHY) layerreferred to as PHY 201 at the UE 200 and PHY 211 at the gNB 210, mediumaccess control (MAC) layer referred to as MAC 202 at the UE 200 and MAC212 at the gNB 210, radio link control (RLC) layer referred to as RLC203 at the UE 200 and RLC 213 at the gNB 210, packet data convergenceprotocol (PDCP) layer referred to as PDCP 204 at the UE 200 and PDCP 214at the gNB 210, and service data application protocol (SDAP) layerreferred to as SDAP 205 at the UE 200 and SDAP 215 at the gNB 210. ThePHY layer, also known as layer 1 (L1), offers transport services tohigher layers. The other four layers of the protocol stack (MAC, RLC,PDCP and SDAP) are collectively known as layer 2 (L2).

FIG. 2B shows an example of the protocol stack for the control plan ofan NR Uu interface in accordance with several of various embodiments ofthe present disclosure. Some of the protocol layers (PHY, MAC, RLC andPDCP) are common between the user plane protocol stack shown in FIG. 2Aand the control plan protocol stack. The control plane protocol stackalso includes the RRC layer, referred to RRC 206 at the UE 200 and RRC216 at the gNB 210, that also terminates at the UE 200 and the gNB 210.In addition, the control plane protocol stack includes the NAS layerthat terminates at the UE 200 and the AMF 220. In FIG. 2B, the NAS layeris referred to as NAS 207 at the UE 200 and NAS 227 at the AMF 220.

FIG. 3 shows example functions and services offered to other layers by alayer in the NR user plane protocol stack of FIG. 2A in accordance withseveral of various embodiments of the present disclosure. For example,the SDAP layer of FIG. 3 (shown in FIG. 2A as SDAP 205 at the UE sideand SDAP 215 at the gNB side) may perform mapping and de-mapping of QoSflows to data radio bearers. The mapping and de-mapping may be based onQoS (e.g., delay, throughput, jitter, error rate, etc.) associated witha QoS flow. A QoS flow may be a QoS differentiation granularity for aPDU session which is a logical connection between a UE 200 and a datanetwork. A PDU session may contain one or more QoS flows. The functionsand services of the SDAP layer include mapping and de-mapping betweenone or more QoS flows and one or more data radio bearers. The SDAP layermay also mark the uplink and/or downlink packets with a QoS flow ID(QFI).

The PDCP layer of FIG. 3 (shown in FIG. 2A as PDCP 204 at the UE sideand PDCP 214 at the gNB side) may perform header compression anddecompression (e.g., using Robust Header Compression (ROHC) protocol) toreduce the protocol header overhead, ciphering and deciphering andintegrity protection and verification to enhance the security over theair interface, reordering and in-order delivery of packets anddiscarding of duplicate packets. A UE may be configured with one PDCPentity per bearer.

In an example scenario not shown in FIG. 3 , a UE may be configured withdual connectivity and may connect to two different cell groups providedby two different base stations. For example, a base station of the twobase stations may be referred to as a master base station and a cellgroup provided by the master base station may be referred to as a mastercell group (MCG). The other base station of the two base stations may bereferred to as a secondary base station and the cell group provided bythe secondary base station may be referred to as a secondary cell group(SCG). A bearer may be configured for the UE as a split bearer that maybe handled by the two different cell groups. The PDCP layer may performrouting of packets corresponding to a split bearer to and/or from RLCchannels associated with the cell groups.

In an example scenario not shown in FIG. 3 , a bearer of the UE may beconfigured (e.g., with control signaling) with PDCP packet duplication.A bearer configured with PDCP duplication may be mapped to a pluralityof RLC channels each corresponding to different one or more cells. ThePDCP layer may duplicate packets of the bearer configured with PDCPduplication and the duplicated packets may be mapped to the differentRLC channels. With PDCP packet duplication, the likelihood of correctreception of packets increases thereby enabling higher reliability.

The RLC layer of FIG. 3 (shown in FIG. 2A as RLC 203 at the UE side andRLC 213 at the gNB side) provides service to upper layers in the form ofRLC channels. The RLC layer may include three transmission modes:transparent mode (TM), Unacknowledged mode (UM) and Acknowledged mode(AM). The RLC layer may perform error correction through automaticrepeat request (ARQ) for the AM transmission mode, segmentation of RLCservice data units (SDUs) for the AM and UM transmission modes andre-segmentation of RLC SDUs for AM transmission mode, duplicatedetection for the AM transmission mode, RLC SDU discard for the AM andUM transmission modes, etc. The UE may be configured with one RLC entityper RLC channel.

The MAC layer of FIG. 3 (shown in FIG. 2A as MAC 202 at the UE side andMAC 212 at the gNB side) provides services to the RLC layer in form oflogical channels. The MAC layer may perform mapping between logicalchannels and transport channels, multiplexing/demultiplexing of MAC SDUsbelonging to one or more logical channels into/from transport blocks(TBs) delivered to/from the physical layer on transport channels,reporting of scheduling information, error correction through hybridautomatic repeat request (HARQ), priority handling between UEs by meansof dynamic scheduling, priority handling between logical channels of oneUE by means of logical channel prioritization and/or padding. In case ofcarrier aggregation, a MAC entity may comprise one HARQ entity per cell.A MAC entity may support multiple numerologies, transmission timings andcells. The control signaling may configure logical channels with mappingrestrictions. The mapping restrictions in logical channel prioritizationmay control the numerology(ies), cell(s), and/or transmissiontiming(s)/duration(s) that a logical channel may use.

The PHY layer of FIG. 3 (shown in FIG. 2A as PHY 201 at the UE side andPHY 211 at the gNB side) provides transport services to the MAC layer inform of transport channels. The physical layer may handlecoding/decoding, HARQ soft combining, rate matching of a coded transportchannel to physical channels, mapping of coded transport channels tophysical channels, modulation and demodulation of physical channels,frequency and time synchronization, radio characteristics measurementsand indication to higher layers, RF processing, and mapping to antennasand radio resources.

FIG. 4 shows example processing of packets at different protocol layersin accordance with several of various embodiments of the presentdisclosure. In this example, three Internet Protocol (IP) packets thatare processed by the different layers of the NR protocol stack. The termSDU shown in FIG. 4 is the data unit that is entered from/to a higherlayer. In contrast, a protocol data unit (PDU) is the data unit that isentered to/from a lower layer. The flow of packets in FIG. 4 is fordownlink. An uplink data flow through layers of the NR protocol stack issimilar to FIG. 4 . In this example, the two leftmost IP packets aremapped by the SDAP layer (shown as SDAP 205 and SDAP 215 in FIG. 2A) toradio bearer 402 and the rightmost packet is mapped by the SDAP layer tothe radio bearer 404. The SDAP layer adds SDAP headers to the IP packetswhich are entered into the PDCP layer as PDCP SDUs. The PDCP layer isshown as PDCP 204 and PDCP 214 in FIG. 2A. The PDCP layer adds the PDCPheaders to the PDCP SDUs which are entered into the RLC layer as RLCSDUs. The RLC layer is shown as RLC 203 and RLC 213 in FIG. 2A. An RLCSDU may be segmented at the RLC layer. The RLC layer adds RLC headers tothe RLC SDUs after segmentation (if segmented) which are entered intothe MAC layer as MAC SDUs. The MAC layer adds the MAC headers to the MACSDUs and multiplexes one or more MAC SDUs to form a PHY SDU (alsoreferred to as a transport block (TB) or a MAC PDU).

In FIG. 4 , the MAC SDUs are multiplexed to form a transport block. TheMAC layer may multiplex one or more MAC control elements (MAC CEs) withzero or more MAC SDUs to form a transport block. The MAC CEs may also bereferred to as MAC commands or MAC layer control signaling and may beused for in-band control signaling. The MAC CEs may be transmitted by abase station to a UE (e.g., downlink MAC CEs) or by a UE to a basestation (e.g., uplink MAC CEs). The MAC CEs may be used for transmissionof information useful by a gNB for scheduling (e.g., buffer statusreport (BSR) or power headroom report (PHR)), activation/deactivation ofone or more cells, activation/deactivation of configured radio resourcesfor or one or more processes, activation/deactivation of one or moreprocesses, indication of parameters used in one or more processes, etc.

FIG. 5A and FIG. 5B show example mapping between logical channels,transport channels and physical channels for downlink and uplink,respectively in accordance with several of various embodiments of thepresent disclosure. As discussed before, the MAC layer provides servicesto higher layer in the form of logical channels. A logical channel maybe classified as a control channel, if used for transmission of controland/or configuration information, or a traffic channel if used fortransmission of user data. Example logical channels in NR includeBroadcast Control Channel (BCCH) used for transmission of broadcastsystem control information, Paging Control Channel (PCCH) used forcarrying paging messages for wireless devices with unknown locations,Common Control Channel (CCCH) used for transmission of controlinformation between UEs and network and for UEs that have no RRCconnection with the network, Dedicated Control Channel (DCCH) which is apoint-to-point bi-directional channel for transmission of dedicatedcontrol information between a UE that has an RRC connection and thenetwork and Dedicated Traffic Channel (DTCH) which is point-to-pointchannel, dedicated to one UE, for the transfer of user information andmay exist in both uplink and downlink.

As discussed before, the PHY layer provides services to the MAC layerand higher layers in the form of transport channels. Example transportchannels in NR include Broadcast Channel (BCH) used for transmission ofpart of the BCCH referred to as master information block (MIB), DownlinkShared Channel (DL-SCH) used for transmission of data (e.g., from DTCHin downlink) and various control information (e.g., from DCCH and CCCHin downlink and part of the BCCH that is not mapped to the BCH), UplinkShared Channel (UL-SCH) used for transmission of uplink data (e.g., fromDTCH in uplink) and control information (e.g., from CCCH and DCCH inuplink) and Paging Channel (PCH) used for transmission of paginginformation from the PCCH. In addition, Random Access Channel (RACH) isa transport channel used for transmission of random access preambles.The RACH does not carry a transport block. Data on a transport channel(except RACH) may be organized in transport blocks, wherein One or moretransport blocks may be transmitted in a transmission time interval(TTI).

The PHY layer may map the transport channels to physical channels. Aphysical channel may correspond to time-frequency resources that areused for transmission of information from one or more transportchannels. In addition to mapping transport channels to physicalchannels, the physical layer may generate control information (e.g.,downlink control information (DCI) or uplink control information (UCI))that may be carried by the physical channels. Example DCI includescheduling information (e.g., downlink assignments and uplink grants),request for channel state information report, power control command,etc. Example UCI include HARQ feedback indicating correct or incorrectreception of downlink transport blocks, channel state informationreport, scheduling request, etc. Example physical channels in NR includea Physical Broadcast Channel (PBCH) for carrying information from theBCH, a Physical Downlink Shared Channel (PDSCH) for carrying informationform the PCH and the DL-SCH, a Physical Downlink Control Channel (PDCCH)for carrying DCI, a Physical Uplink Shared Channel (PUSCH) for carryinginformation from the UL-SCH and/or UCI, a Physical Uplink ControlChannel (PUCCH) for carrying UCI and Physical Random Access Channel(PRACH) for transmission of RACH (e.g., random access preamble).

The PHY layer may also generate physical signals that are not originatedfrom higher layers. As shown in FIG. 5A, example downlink physicalsignals include Demodulation Reference Signal (DM-RS), Phase TrackingReference Signal (PT-RS), Channel State Information Reference Signal(CSI-RS), Primary Synchronization Signal (PSS) and SecondarySynchronization Signal (SSS). As shown in FIG. 5B, example uplinkphysical signals include DM-RS, PT-RS and sounding reference signal(SRS).

As indicated earlier, some of the protocol layers (PHY, MAC, RLC andPDCP) of the control plane of an NR Uu interface, are common between theuser plane protocol stack (as shown in FIG. 2A) and the control planeprotocol stack (as shown in FIG. 2B). In addition to PHY, MAC, RLC andPDCP, the control plane protocol stack includes the RRC protocol layerand the NAS protocol layer.

The NAS layer, as shown in FIG. 2B, terminates at the UE 200 and the AMF220 entity of the 5G-C 130. The NAS layer is used for core networkrelated functions and signaling including registration, authentication,location update and session management. The NAS layer uses services fromthe AS of the Uu interface to transmit the NAS messages.

The RRC layer, as shown in FIG. 2B, operates between the UE 200 and thegNB 210 (more generally NG-RAN 120) and may provide services andfunctions such as broadcast of system information (SI) related to AS andNAS as well as paging initiated by the 5G-C 130 or NG-RAN 120. Inaddition, the RRC layer is responsible for establishment, maintenanceand release of an RRC connection between the UE 200 and the NG-RAN 120,carrier aggregation configuration (e.g., addition, modification andrelease), dual connectivity configuration (e.g., addition, modificationand release), security related functions, radio bearerconfiguration/maintenance and release, mobility management (e.g.,maintenance and context transfer), UE cell selection and reselection,inter-RAT mobility, QoS management functions, UE measurement reportingand control, radio link failure (RLF) detection and NAS messagetransfer. The RRC layer uses services from PHY, MAC, RLC and PDCP layersto transmit RRC messages using signaling radio bearers (SRBs). The SRBsare mapped to CCCH logical channel during connection establishment andto DCCH logical channel after connection establishment.

FIG. 6 shows example physical layer processes for signal transmission inaccordance with several of various embodiments of the presentdisclosure. Data and/or control streams from MAC layer may beencoded/decoded to offer transport and control services over the radiotransmission link. For example, one or more (e.g., two as shown in FIG.6 ) transport blocks may be received from the MAC layer for transmissionvia a physical channel (e.g., a physical downlink shared channel or aphysical uplink shared channel). A cyclic redundancy check (CRC) may becalculated and attached to a transport block in the physical layer. TheCRC calculation may be based on one or more cyclic generatorpolynomials. The CRC may be used by the receiver for error detection.Following the transport block CRC attachment, a low-density parity check(LDPC) base graph selection may be performed. In example embodiments,two LDPC base graphs may be used wherein a first LDPC base graph may beoptimized for small transport blocks and a second LDPC base graph may beoptimized for comparatively larger transport blocks.

The transport block may be segmented into code blocks and code block CRCmay be calculated and attached to a code block. A code block may be LDPCcoded and the LDPC coded blocks may be individually rate matched. Thecode blocks may be concatenated to create one or more codewords. Thecontents of a codeword may be scrambled and modulated to generate ablock of complex-valued modulation symbols. The modulation symbols maybe mapped to a plurality of transmission layers (e.g., multiple-inputmultiple-output (MIMO) layers) and the transmission layers may besubject to transform precoding and/or precoding. The precodedcomplex-valued symbols may be mapped to radio resources (e.g., resourceelements). The signal generator block may create a baseband signal andup-convert the baseband signal to a carrier frequency for transmissionvia antenna ports. The signal generator block may employ mixers, filtersand/or other radio frequency (RF) components prior to transmission viathe antennas. The functions and blocks in FIG. 6 are illustrated asexamples and other mechanisms may be implemented in various embodiments.

FIG. 7 shows examples of RRC states and RRC state transitions at a UE inaccordance with several of various embodiments of the presentdisclosure. A UE may be in one of three RRC states: RRC_IDLE 702, RRCINACTIVE 704 and RRC_CONNECTED 706. In RRC_IDLE 702 state, no RRCcontext (e.g., parameters needed for communications between the UE andthe network) may be established for the UE in the RAN. In RRC_IDLE 702state, no data transfer between the UE and the network may take placeand uplink synchronization is not maintained. The wireless device maysleep most of the time and may wake up periodically to receive pagingmessages. The uplink transmission of the UE may be based on a randomaccess process and to enable transition to the RRC_CONNECTED 706 state.The mobility in RRC_IDLE 702 state is through a cell reselectionprocedure where the UE camps on a cell based on one or more criteriaincluding signal strength that is determined based on the UEmeasurements.

In RRC_CONNECTED 706 state, the RRC context is established and both theUE and the RAN have necessary parameters to enable communicationsbetween the UE and the network. In the RRC_CONNECTED 706 state, the UEis configured with an identity known as a Cell Radio Network TemporaryIdentifier (C-RNTI) that is used for signaling purposes (e.g., uplinkand downlink scheduling, etc.) between the UE and the RAN. The wirelessdevice mobility in the RRC_CONNECTED 706 state is managed by the RAN.The wireless device provides neighboring cells and/or current servingcell measurements to the network and the network may make hand overdecisions. Based on the wireless device measurements, the currentserving base station may send a handover request message to aneighboring base station and may send a handover command to the wirelessdevice to handover to a cell of the neighboring base station. Thetransition of the wireless device from the RRC_IDLE 702 state to theRRC_CONNECTED 706 state or from the RRC_CONNECTED 706 state to theRRC_IDLE 702 state may be based on connection establishment andconnection release procedures (shown collectively as connectionestablishment/release 710 in FIG. 7 ).

To enable a faster transition to the RRC_CONNECTED 706 state (e.g.,compared to transition from RRC_IDLE 702 state to RRC_CONNECTED 706state), an RRC_INACTIVE 704 state is used for an NR UE wherein, the RRCcontext is kept at the UE and the RAN. The transition from theRRC_INACTIVE 704 state to the RRC_CONNECTED 706 state is handled by RANwithout CN signaling. Similar to the RRC_IDLE 702 state, the mobility inRRC_INACTIVE 704 state is based on a cell reselection procedure withoutinvolvement from the network. The transition of the wireless device fromthe RRC_INACTIVE 704 state to the RRC_CONNECTED 706 state or from theRRC_CONNECTED 706 state to the RRC_INACTIVE 704 state may be based onconnection resume and connection inactivation procedures (showncollectively as connection resume/inactivation 712 in FIG. 7 ). Thetransition of the wireless device from the RRC_INACTIVE 704 state to theRRC_IDLE 702 state may be based on a connection release 714 procedure asshown in FIG. 7 .

In NR, Orthogonal Frequency Division Multiplexing (OFDM), also calledcyclic prefix OFDM (CP-OFDM), is the baseline transmission scheme inboth downlink and uplink of NR and the Discrete Fourier Transform (DFT)spread OFDM (DFT-s-OFDM) is a complementary uplink transmission inaddition to the baseline OFDM scheme. OFDM is multi-carrier transmissionscheme wherein the transmission bandwidth may be composed of severalnarrowband sub-carriers. The subcarriers are modulated by the complexvalued OFDM modulation symbols resulting in an OFDM signal. The complexvalued OFDM modulation symbols are obtained by mapping, by a modulationmapper, the input data (e.g., binary digits) to different points of amodulation constellation diagram. The modulation constellation diagramdepends on the modulation scheme. NR may use different types ofmodulation schemes including Binary Phase Shift Keying (BPSK), π/2-BPSK,Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation(16QAM), 64QAM and 256QAM. Different and/or higher order modulationschemes (e.g., M-QAM in general) may be used. An OFDM signal with Nsubcarriers may be generated by processing N subcarriers in parallel forexample by using Inverse Fast Fourier Transform (IFFT) processing. TheOFDM receiver may use FFT processing to recover the transmitted OFDMmodulation symbols. The subcarrier spacing of subcarriers in an OFDMsignal is inversely proportional to an OFDM modulation symbol duration.For example, for a 15 KHz subcarrier spacing, duration of an OFDM signalis nearly 66.74 μs. To enhance the robustness of OFDM transmission intime dispersive channels, a cyclic prefix (CP) may be inserted at thebeginning of an OFDM symbol. For example, the last part of an OFDMsymbol may be copied and inserted at the beginning of an OFDM symbol.The CP insertion enhanced the OFDM transmission scheme by preservingsubcarrier orthogonality in time dispersive channels.

In NR, different numerologies may be used for OFDM transmission. Anumerology of OFDM transmission may indicate a subcarrier spacing and aCP duration for the OFDM transmission. For example, a subcarrier spacingin NR may generally be a multiple of 15 KHz and expressed as Δf=2^(μ)·15KHz (μ=0, 1, 2, . . . ). Example subcarrier spacings used in NR include15 KHz (μ=0), 30 KHz (μ=1), 60 KHz (μ=2), 120 KHz (μ=3) and 240 KHz(μ=4). As discussed before, a duration of OFDM symbol is inverselyproportional to the subcarrier spacing and therefor OFDM symbol durationmay depend on the numerology (e.g. the p value).

FIG. 8 shows an example time domain transmission structure in NR whereinOFDM symbols are grouped into slots, subframes and frames in accordancewith several of various embodiments of the present disclosure. A slot isa group of N_(symb) ^(slot) OFDM symbols, wherein the N_(symb) ^(slot)may have a constant value (e.g., 14). Since different numerologiesresults in different OFDM symbol durations, duration of a slot may alsodepend on the numerology and may be variable. A subframe may have aduration of 1 ms and may be composed of one or more slots, the number ofwhich may depend on the slot duration. The number of slots per subframeis therefore a function of p and may generally expressed as N_(slot)^(subframe,μ) and the number of symbols per subframe may be expressed asN_(symb) ^(subframe,μ)=N_(symb) ^(slot)N_(slot) ^(subframe,μ). A framemay have a duration of 10 ms and may consist of 10 subframes. The numberof slots per frame may depend on the numerology and therefore may bevariable. The number of slots per frame may generally be expressed asN_(slot) ^(frame,μ).

An antenna port may be defined as a logical entity such that channelcharacteristics over which a symbol on the antenna port is conveyed maybe inferred from the channel characteristics over which another symbolon the same antenna port is conveyed. For example, for DM-RS associatedwith a PDSCH, the channel over which a PDSCH symbol on an antenna portis conveyed may be inferred from the channel over which a DM-RS symbolon the same antenna port is conveyed, for example, if the two symbolsare within the same resource as the scheduled PDSCH and/or in the sameslot and/or in the same precoding resource block group (PRG). Forexample, for DM-RS associated with a PDCCH, the channel over which aPDCCH symbol on an antenna port is conveyed may be inferred from thechannel over which a DM-RS symbol on the same antenna port is conveyedif, for example, the two symbols are within resources for which the UEmay assume the same precoding being used. For example, for DM-RSassociated with a PBCH, the channel over which a PBCH symbol on oneantenna port is conveyed may be inferred from the channel over which aDM-RS symbol on the same antenna port is conveyed if, for example, thetwo symbols are within a SS/PBCH block transmitted within the same slot,and with the same block index. The antenna port may be different from aphysical antenna. An antenna port may be associated with an antenna portnumber and different physical channels may correspond to differentranges of antenna port numbers.

FIG. 9 shows an example of time-frequency resource grid in accordancewith several of various embodiments of the present disclosure. Thenumber of subcarriers in a carrier bandwidth may be based on thenumerology of OFDM transmissions in the carrier. A resource element,corresponding to one symbol duration and one subcarrier, may be thesmallest physical resource in the time-frequency grid. A resourceelement (RE) for antenna port p and subcarrier spacing configuration μmay be uniquely identified by (k,l)_(p,μ) where k is the index of asubcarrier in the frequency domain and l may refer to the symbolposition in the time domain relative to some reference point. A resourceblock may be defined as N_(SC) ^(RB)=12 subcarriers. Since subcarrierspacing depends on the numerology of OFDM transmission, the frequencydomain span of a resource block may be variable and may depend on thenumerology. For example, for a subcarrier spacing of 15 KHz (e.g., μ=0),a resource block may be 180 KHz and for a subcarrier spacing of 30 KHz(e.g., μ=1), a resource block may be 360 KHz.

With large carrier bandwidths defined in NR and due to limitedcapabilities for some UEs (e.g., due to hardware limitations), a UE maynot support an entire carrier bandwidth. Receiving on the full carrierbandwidth may imply high energy consumption. For example, transmittingdownlink control channels on the full downlink carrier bandwidth mayresult in high power consumption for wide carrier bandwidths. NR may usea bandwidth adaptation procedure to dynamically adapt the transmit andreceive bandwidths. The transmit and receive bandwidth of a UE on a cellmay be smaller than the bandwidth of the cell and may be adjusted. Forexample, the width of the transmit and/or receive bandwidth may change(e.g. shrink during period of low activity to save power); the locationof the transmit and/or receive bandwidth may move in the frequencydomain (e.g. to increase scheduling flexibility); and the subcarrierspacing of the transmit or receive bandwidth may change (e.g. to allowdifferent services). A subset of the cell bandwidth may be referred toas a Bandwidth Part (BWP) and bandwidth adaptation may be achieved byconfiguring the UE with one or more BWPs. The base station may configurea UE with a set of downlink BWPs and a set of uplink BWPs. A BWP may becharacterized by a numerology (e.g., subcarrier spacing and cyclicprefix) and a set of consecutive resource blocks in the numerology ofthe BWP. One or more first BWPs of the one or more BWPs of the cell maybe active at a time. An active BWP may be an active downlink BWP or anactive uplink BWP.

FIG. 10 shows an example of bandwidth part adaptation and switching. Inthis example, three BWPs (BWP₁ 1004, BWP₂ 1006 and BWP₃ 1008) areconfigured for a UE on a carrier bandwidth. The BWP₁ is configured witha bandwidth of 40 MHz and a numerology with subcarrier spacing of 15KHz, the BWP₂ is configured with a bandwidth of 10 MHz and a numerologywith subcarrier spacing of 15 KHz and the BWP₃ is configured with abandwidth of 20 MHz and a subcarrier spacing of 60 KHz. The wirelessdevice may switch from a first BWP (e.g., BWP₁) to a second BWP (e.g.,BWP₂). An active BWP of the cell may change from the first BWP to thesecond BWP in response to the BWP switching.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10 ) may be based on acommand from the base station. The command may be a DCI comprisingscheduling information for the UE in the second BWP. In case of uplinkBWP switching, the first BWP and the second BWP may be uplink BWPs andthe scheduling information may be an uplink grant for uplinktransmission via the second BWP. In case of downlink BWP switching, thefirst BWP and the second BWP may be downlink BWPs and the schedulinginformation may be a downlink assignment for downlink reception via thesecond BWP.

The BWP switching (e.g., BWP switching 1010, BWP switching 1012, BWPswitching 1014, or BWP switching 1016 in FIG. 10 ) may be based on anexpiry of a timer. The base station may configure a wireless device witha BWP inactivity timer and the wireless device may switch to a defaultBWP (e.g., default downlink BWP) based on the expiry of the BWPinactivity timer. The expiry of the BWP inactivity timer may be anindication of low activity on the current active downlink BWP. The basestation may configure the wireless device with the default downlink BWP.If the base station does not configure the wireless device with thedefault BWP, the default BWP may be an initial downlink BWP. The initialactive BWP may be the BWP that the wireless device receives schedulinginformation for remaining system information upon transition to anRRC_CONNECTED state.

A wireless device may monitor a downlink control channel of a downlinkBWP. For example, the UE may monitor a set of PDCCH candidates inconfigured monitoring occasions in one or more configured COntrolREsource SETs (CORESETs) according to the corresponding search spaceconfigurations. A search space configuration may define how/where tosearch for PDCCH candidates. For example, the search space configurationparameters may comprise a monitoring periodicity and offset parameterindicating the slots for monitoring the PDCCH candidates. The searchspace configuration parameters may further comprise a parameterindicating a first symbol with a slot within the slots determined formonitoring PDCCH candidates. A search space may be associated with oneor more CORESETs and the search space configuration may indicate one ormore identifiers of the one or more CORESETs. The search spaceconfiguration parameters may further indicate that whether the searchspace is a common search space or a UE-specific search space. A commonsearch space may be monitored by a plurality of wireless devices and aUE-specific search space may be dedicated to a specific UE.

FIG. 11A shows example arrangements of carriers in carrier aggregationin accordance with several of various embodiments of the presentdisclosure. With carrier aggregation, multiple NR component carriers(CCs) may be aggregated. Downlink transmissions to a wireless device maytake place simultaneously on the aggregated downlink CCs resulting inhigher downlink data rates. Uplink transmissions from a wireless devicemay take place simultaneously on the aggregated uplink CCs resulting inhigher uplink data rates. The component carriers in carrier aggregationmay be on the same frequency band (e.g., intra-band carrier aggregation)or on different frequency bands (e.g., inter-band carrier aggregation).The component carriers may also be contiguous or non-contiguous. Thisresults in three possible carrier aggregation scenarios, intra-bandcontiguous CA 1102, intra-band non-contiguous CA 1104 and inter-band CA1106 as shown in FIG. 11A. Depending on the UE capability for carrieraggregation, a UE may transmit and/or receive on multiple carriers orfor a UE that is not capable of carrier aggregation, the UE may transmitand/or receive on one component carrier at a time. In this disclosure,the carrier aggregation is described using the term cell and a carrieraggregation capable UE may transmit and/or receive via multiple cells.

In carrier aggregation, a UE may be configured with multiple cells. Acell of the multiple cells configured for the UE may be referred to as aPrimary Cell (PCell). The PCell may be the first cell that the UE isinitially connected to. One or more other cells configured for the UEmay be referred to as Secondary Cells (SCells). The base station mayconfigure a UE with multiple SCells. The configured SCells may bedeactivated upon configuration and the base station may dynamicallyactivate or deactivate one or more of the configured SCells based ontraffic and/or channel conditions. The base station may activate ordeactivate configured SCells using a SCell Activation/Deactivation MACCE. The SCell Activation/Deactivation MAC CE may comprise a bitmap,wherein each bit in the bitmap may correspond to a SCell and the valueof the bit indicates an activation status or deactivation status of theSCell.

An SCell may also be deactivated in response to expiry of a SCelldeactivation timer of the SCell. The expiry of an SCell deactivationtimer of an SCell may be an indication of low activity (e.g., lowtransmission or reception activity) on the SCell. The base station mayconfigure the SCell with an SCell deactivation timer. The base stationmay not configure an SCell deactivation timer for an SCell that isconfigured with PUCCH (also referred to as a PUCCH SCell). Theconfiguration of the SCell deactivation timer may be per configuredSCell and different SCells may be configured with different SCelldeactivation timer values. The SCell deactivation timer may be restartedbased on one or more criteria including reception of downlink controlinformation on the SCell indicating uplink grant or downlink assignmentfor the SCell or reception of downlink control information on ascheduling cell indicating uplink grant or downlink assignment for theSCell or transmission of a MAC PDU based on a configured uplink grant orreception of a configured downlink assignment.

A PCell for a UE may be an SCell for another UE and a SCell for a UE maybe PCell for another UE. The configuration of PCell may be UE-specific.One or more SCells of the multiple SCells configured for a UE may beconfigured as downlink-only SCells, e.g., may only be used for downlinkreception and may not be used for uplink transmission. In case ofself-scheduling, the base station may transmit signaling for uplinkgrants and/or downlink assignments on the same cell that thecorresponding uplink or downlink transmission takes place. In case ofcross-carrier scheduling, the base station may transmit signaling foruplink grants and/or downlink assignments on a cell different from thecell that the corresponding uplink or downlink transmission takes place.

FIG. 11B shows examples of uplink control channel groups in accordancewith several of various embodiments of the present disclosure. A basestation may configure a UE with multiple PUCCH groups wherein a PUCCHgroup comprises one or more cells. For example, as shown in FIG. 11B,the base station may configure a UE with a primary PUCCH group 1114 anda secondary PUCCH group 1116. The primary PUCCH group may comprise thePCell 1110 and one or more first SCells. First UCI corresponding to thePCell and the one or more first SCells of the primary PUCCH group may betransmitted by the PUCCH of the PCell. The first UCI may be, forexample, HARQ feedback for downlink transmissions via downlink CCs ofthe PCell and the one or more first SCells. The secondary PUCCH groupmay comprise a PUCCH SCell and one or more second SCells. Second UCIcorresponding to the PUCCH SCell and the one or more second SCells ofthe secondary PUCCH group may be transmitted by the PUCCH of the PUCCHSCell. The second UCI may be, for example, HARQ feedback for downlinktransmissions via downlink CCs of the PUCCH SCell and the one or moresecond SCells.

FIG. 12A, FIG. 12B and FIG. 12C show example random access processes inaccordance with several of various embodiments of the presentdisclosure. FIG. 12A shows an example of four step contention-basedrandom access (CBRA) procedure. The four-step CBRA procedure includesexchanging four messages between a UE and a base station. Msg1 may befor transmission (or retransmission) of a random access preamble by thewireless device to the base station. Msg2 may be the random accessresponse (RAR) by the base station to the wireless device. Msg3 is thescheduled transmission based on an uplink grant indicated in Msg2 andMsg4 may be for contention resolution.

The base station may transmit one or more RRC messages comprisingconfiguration parameters of the random access parameters. The randomaccess parameters may indicate radio resources (e.g., time-frequencyresources) for transmission of the random access preamble (e.g., Msg1),configuration index, one or more parameters for determining the power ofthe random access preamble (e.g., a power ramping parameter, a preamblereceived target power, etc.), a parameter indicating maximum number ofpreamble transmission, RAR window for monitoring RAR, cell-specificrandom access parameters and UE specific random access parameters. TheUE-specific random access parameters may indicate one or more PRACHoccasions for random access preamble (e.g., Msg1) transmissions. Therandom access parameters may indicate association between the PRACHoccasions and one or more reference signals (e.g., SSB or CSI-RS). Therandom access parameters may further indicate association between therandom access preambles and one or more reference signals (e.g., SBB orCSI-RS). The UE may use one or more reference signals (e.g., SSB(s) orCSI-RS(s)) and may determine a random access preamble to use for Msg1transmission based on the association between the random accesspreambles and the one or more reference signals. The UE may use one ormore reference signals (e.g., SSB(s) or CSI-RS(s)) and may determine thePRACH occasion to use for Msg1 transmission based on the associationbetween the PRACH occasions and the reference signals. The UE mayperform a retransmission of the random access preamble if no response isreceived with the RAR window following the transmission of the preamble.UE may use a higher transmission power for retransmission of thepreamble. UE may determine the higher transmission power of the preamblebased on the power ramping parameter.

Msg2 is for transmission of RAR by the base station. Msg2 may comprise aplurality of RARs corresponding to a plurality of random accesspreambles transmitted by a plurality of UEs. Msg2 may be associated witha random access temporary radio identifier (RA-RNTI) and may be receivedin a common search space of the UE. The RA-RNTI may be based on thePRACH occasion (e.g., time and frequency resources of a PRACH) in whicha random access preamble is transmitted. RAR may comprise a timingadvance command for uplink timing adjustment at the UE, an uplink grantfor transmission of Msg3 and a temporary C-RNTI. In response to thesuccessful reception of Msg2, the UE may transmit the Msg3. Msg3 andMsg4 may enable contention resolution in case of CBRA. In a CBRA, aplurality of UEs may transmit the same random access preamble and mayconsider the same RAR as being corresponding to them. UE may include adevice identifier in Msg3 (e.g., a C-RNTI, temporary C-RNTI or other UEidentity). Base station may transmit the Msg4 with a PDSCH and UE mayassume that the contention resolution is successful in response to thePDSCH used for transmission of Msg4 being associated with the UEidentifier included in Msg3.

FIG. 12B shows an example of a contention-free random access (CFRA)process. Msg 1 (random access preamble) and Msg 2 (random accessresponse) in FIG. 12B for CFRA may be analogous to Msg 1 and Msg 2 inFIG. 12A for CBRA. In an example, the CFRA procedure may be initiated inresponse to a PDCCH order from a base station. The PDCCH order forinitiating the CFRA procedure by the wireless device may be based on aDCI having a first format (e.g., format 1_0). The DCI for the PDCCHorder may comprise a random access preamble index, an UL/SUL indicatorindicating an uplink carrier of a cell (e.g., normal uplink carrier orsupplementary uplink carrier) for transmission of the random accesspreamble, a SS/PBCH index indicating the SS/PBCH that may be used todetermine a RACH occasion for PRACH transmission, a PRACH mask indexindicating the RACH occasion associated with the SS/PBCH indicated bythe SS/PBCH index for PRACH transmission, etc. In an example, the CFRAprocess may be started in response to a beam failure recovery process.The wireless device may start the CFRA for the beam failure recoverywithout a command (e.g., PDCCH order) from the base station and by usingthe wireless device dedicated resources.

FIG. 12C shows an example of a two-step random access process comprisingtwo messages exchanged between a wireless device and a base station. MsgA may be transmitted by the wireless device to the base station and maycomprise one or more transmissions of a preamble and/or one or moretransmissions of a transport block. The transport block in Msg A and Msg3 in FIG. 12A may have similar and/or equivalent contents. The transportblock of Msg A may comprise data and control information (e.g., SR, HARQfeedback, etc.). In response to the transmission of Msg A, the wirelessdevice may receive Msg B from the base station. Msg B in FIG. 12C andMsg 2 (e.g., RAR) illustrated in FIGS. 12A and 12B may have similarand/or equivalent content.

The base station may periodically transmit synchronization signals(SSs), e.g., primary SS (PSS) and secondary SS (SSS) along with PBCH oneach NR cell. The PSS/SSS together with PBCH is jointly referred to as aSS/PBCH block. The SS/PBCH block enables a wireless device to find acell when entering to the mobile communications network or find newcells when moving within the network. The SS/PBCH block spans four OFDMsymbols in time domain. The PSS is transmitted in the first symbol andoccupies 127 subcarriers in frequency domain. The SSS is transmitted inthe third OFDM symbol and occupies the same 127 subcarriers as the PSS.The are eight and nine empty subcarriers on each side of the SSS. ThePBCH is transmitted on the second OFDM symbol occupying 240 subcarriers,the third OFDM symbol occupying 48 subcarriers on each side of the SSS,and on the fourth OFDM symbol occupying 240 subcarriers. Some of thePBCH resources indicated above may be used for transmission of thedemodulation reference signal (DMRS) for coherent demodulation of thePBCH. The SS/PBCH block is transmitted periodically with a periodranging from 5 ms to 160 ms. For initial cell search or for cell searchduring inactive/idle state, a wireless device may assume that that theSS/PBCH block is repeated at least every 20 ms.

In NR, transmissions using of antenna arrays, with many antennaelements, and beamforming plays an important role specially in higherfrequency bands. Beamforming enables higher capacity by increasing thesignal strength (e.g., by focusing the signal energy in a specificdirection) and by lowering the amount interference received at thewireless devices. The beamforming techniques may generally be divided toanalog beamforming and digital beamforming techniques. With digitalbeamforming, signal processing for beamforming is carried out in thedigital domain before digital-to-analog conversion and detailed controlof both amplitude and phase of different antenna elements may bepossible. With analog beamforming, the signal processing for beamformingis carried out in the analog domain and after the digital to analogconversion. The beamformed transmissions may be in one direction at atime. For example, the wireless devices that are in different directionsrelative to the base station may receive their downlink transmissions atdifferent times. For analog receiver-side beamforming, the receiver mayfocus its receiver beam in one direction at a time.

In NR, the base station may use beam sweeping for transmission ofSS/PBCH blocks. The SS/PBCH blocks may be transmitted in different beamsusing time multiplexing. The set of SS/PBCH blocks that are transmittedin one beam sweep may be referred to as a SS/PBCH block set. The periodof PBCH/SSB block transmission may be a time duration between a SS/PBCHblock transmission in a beam and the next SS/PBCH block transmission inthe same beam. The period of SS/PBCH block is, therefore, also theperiod of the SS/PBCH block set.

FIG. 13A shows example time and frequency structure of SS/PBCH blocksand their associations with beams in accordance with several of variousembodiments of the present disclosure. In this example, a SS/PBCH block(also referred to as SSB) set comprise L SSBs wherein an SSB in the SSBset is associated with (e.g., transmitted in) one of L beams of a cell.The transmission of SBBs of an SSB set may be confined within a 5 msinterval, either in a first half-frame or a second half-frame of a 10 msframe. The number of SSBs in an SSB set may depend on the frequency bandof operation. For example, the number of SSBs in a SSB set may be up tofour SSBs in frequency bands below 3 GHz enabling beam sweeping of up tofour beams, up to eight SSBs in frequency bands between 3 GHz and 6 GHzenabling beam sweeping of up to eight beams, and up to sixty four SSBsin higher frequency bands enabling beam sweeping of up to sixty fourbeams. The SSs of an SSB may depend on a physical cell identity (PCI) ofthe cell and may be independent of which beam of the cell is used fortransmission of the SSB. The PBCH of an SSB may indicate a time indexparameter and the wireless device may determine the relative position ofthe SSB within the SSB set using the time index parameter. The wirelessdevice may use the relative position of the SSB within an SSB set fordetermining the frame timing and/or determining RACH occasions for arandom access process.

A wireless device entering the mobile communications network may firstsearch for the PSS. After detecting the PSS, the wireless device maydetermine the synchronization up to the periodicity of the PSS. Bydetecting the PSS, the wireless device may determine the transmissiontiming of the SSS. The wireless device may determine the PCI of the cellafter detecting the SSS. The PBCH of a SS/PBCH block is a downlinkphysical channel that carries the MIB. The MIB may be used by thewireless device to obtain remaining system information (RMSI) that isbroadcast by the network. The RMSI may include System Information Block1 (SIB1) that contains information required for the wireless device toaccess the cell.

As discussed earlier, the wireless device may determine a time indexparameter from the SSB. The PBCH comprises a half-frame parameterindicating whether the SSB is in the first 5 ms half or the second 5 mshalf of a 10 ms frame. The wireless device may determine the frameboundary using the time index parameter and the half-frame parameter. Inaddition, the PBCH may comprise a parameter indicating the system framenumber (SFN) of the cell.

The base station may transmit CSI-RS and a UE may measure the CSI-RS toobtain channel state information (CSI). The base station may configurethe CSI-RS in a UE-specific manner. In some scenarios, same set ofCSI-RS resources may be configured for multiple UEs and one or moreresource elements of a CSI-RS resource may be shared among multiple UEs.A CSI-RS resource may be configured such that it does not collide with aCORESET configured for the wireless device and/or with a DMRS of a PDSCHscheduled for the wireless device and/or transmitted SSBs. The UE maymeasure one or more CSI-RSs configured for the UE and may generate a CSIreport based on the CSI-RS measurements and may transmit the CSI reportto the base station for scheduling, link adaptation and/or otherpurposes.

NR supports flexible CSI-RS configurations. A CSI-RS resource may beconfigured with single or multiple antenna ports and with configurabledensity. Based on the number of configured antenna ports, a CSI-RSresource may span different number of OFDM symbols (e.g., 1, 2, and 4symbols). The CSI-RS may be configured for a downlink BWP and may usethe numerology of the downlink BWP. The CSI-RS may be configured tocover the full bandwidth of the downlink BWP or a portion of thedownlink BWP. In some case, the CSI-RS may be repeated in every resourceblock of the CSI-RS bandwidth, referred to as CSI-RS with density equalto one. In some cases, the CSI-RS may be configured to be repeated inevery other resource block of the CSI-RS bandwidth. CSI-RS may benon-zero power (NZP) CSI-RS or zero-power (ZP) CSI-RS.

The base station may configure a wireless device with one or more setsof NZP CSI-RS resources. The base station may configure the wirelessdevice with a NZP CSI-RS resource set using an RRC information element(IE) NZP-CSI-RS-ResourceSet indicating a NZP CSI-RS resource setidentifier (ID) and parameters specific to the NZP CSI-RS resource set.An NZP CSI-RS resource set may comprise one or more CSI-RS resources. AnNZP CSI-RS resource set may be configured as part of the CSI measurementconfiguration.

The CSI-RS may be configured for periodic, semi-persistent or aperiodictransmission. In case of the periodic and semi-persistent CSI-RSconfigurations, the wireless device may be configured with a CSIresource periodicity and offset parameter that indicate a periodicityand corresponding offset in terms of number of slots. The wirelessdevice may determine the slots that the CSI-RSs are transmitted. Forsemi-persistent CSI-RS, the CSI-RS resources for CSI-RS transmissionsmay be activated and deactivated by using a semi-persistent (SP) CSI-CSIResource Set Activation/Deactivation MAC CE. In response to receiving aMAC CE indicating activation of semi-persistent CSI-RS resources, thewireless device may assume that the CSI-RS transmissions will continueuntil the CSI-RS resources for CSI-RS transmissions are activated.

As discussed before, CSI-RS may be configured for a wireless device asNZP CSI-RS or ZP CSI-RS. The configuration of the ZP CSI-RS may besimilar to the NZP CSI-RS with the difference that the wireless devicemay not carry out measurements for the ZP CSI-RS. By configuring ZPCSI-RS, the wireless device may assume that a scheduled PDSCH thatincludes resource elements from the ZP CSI-RS is rate matched aroundthose ZP CSI-RS resources. For example, a ZP CSI-RS resource configuredfor a wireless device may be an NZP CSI-RS resource for another wirelessdevice. For example, by configuring ZP CSI-RS resources for the wirelessdevice, the base station may indicate to the wireless device that thePDSCH scheduled for the wireless device is rate matched around the ZPCSI-RS resources.

A base station may configure a wireless device with channel stateinformation interference measurement (CSI-IM) resources. Similar to theCSI-RS configuration, configuration of locations and density of CSI-IMresources may be flexible. The CSI-IM resources may be periodic(configured with a periodicity), semi-persistent (configured with aperiodicity and activated and deactivated by MAC CE) or aperiodic(triggered by a DCI).

Tracking reference signals (TRSs) may be configured for a wirelessdevice as a set of sparse reference signals to assist the wireless intime and frequency tracking and compensating time and frequencyvariations in its local oscillator. The wireless device may further usethe TRSs for estimating channel characteristics such as delay spread ordoppler frequency. The base station may use a CSI-RS configuration forconfiguring TRS for the wireless device. The TRS may be configured as aresource set comprising multiple periodic NZP CSI-RS resources.

A base station may configure a UE and the UE may transmit soundingreference signals (SRSs) to enable uplink channel sounding/estimation atthe base station. The SRS may support up to four antenna ports and maybe designed with low cubic metric enabling efficient operation of thewireless device amplifier. The SRS may span one or more (e.g., one, twoor four) consecutive OFDM symbols in time domain and may be locatedwithin the last n (e.g., six) symbols of a slot. In the frequencydomain, the SRS may have a structure that is referred to as a combstructure and may be transmitted on every Nth subcarrier. Different SRStransmissions from different wireless devices may have different combstructures and may be multiplexed in frequency domain.

A base station may configure a wireless device with one or more SRSresource sets and an SRS resource set may comprise one or more SRSresources. The SRS resources in an SRS resources set may be configuredfor periodic, semi-persistent or aperiodic transmission. The periodicSRS and the semi-persistent SRS resources may be configured withperiodicity and offset parameters. The Semi-persistent SRS resources ofa configured semi-persistent SRS resource set may be activated ordeactivated by a semi-persistent (SP) SRS Activation/Deactivation MACCE. The set of SRS resources included in an aperiodic SRS resource setmay be activated by a DCI. A value of a field (e.g., an SRS requestfield) in the DCI may indicate activation of resources in an aperiodicSRS resource set from a plurality of SRS resource sets configured forthe wireless device.

An antenna port may be associated with one or more reference signals.The receiver may assume that the one or more reference signals,associated with the antenna port, may be used for estimating channelcorresponding to the antenna port. The reference signals may be used toderive channel state information related to the antenna port. Twoantenna ports may be referred to as quasi co-located if characteristics(e.g., large-scale properties) of the channel over which a symbol isconveyed on one antenna port may be inferred from the channel over whicha symbol is conveyed from another antenna port. For example, a UE mayassume that radio channels corresponding to two different antenna portshave the same large-scale properties if the antenna ports are specifiedas quasi co-located. In some cases, the UE may assume that two antennaports are quasi co-located based on signaling received from the basestation. Spatial quasi-colocation (QCL) between two signals may be, forexample, due to the two signals being transmitted from the same locationand in the same beam. If a receive beam is good for a signal in a groupof signals that are spatially quasi co-located, it may be assumed alsobe good for the other signals in the group of signals.

The CSI-RS in the downlink and the SRS in uplink may serve asquasi-location (QCL) reference for other physical downlink channels andphysical uplink channels, respectively. For example, a downlink physicalchannel (e.g., PDSCH or PDCCH) may be spatially quasi co-located with adownlink reference signal (e.g., CSI-RS or SSB). The wireless device maydetermine a receive beam based on measurement on the downlink referencesignal and may assume that the determined received beam is also good forreception of the physical channels (e.g., PDSCH or PDCCH) that arespatially quasi co-located with the downlink reference signal.Similarly, an uplink physical channel (e.g., PUSCH or PUCCH) may bespatially quasi co-located with an uplink reference signal (e.g., SRS).The base station may determine a receive beam based on measurement onthe uplink reference signal and may assume that the determined receivedbeam is also good for reception of the physical channels (e.g., PUSCH orPUCCH) that are spatially quasi co-located with the uplink referencesignal.

The Demodulation Reference Signals (DM-RSs) enables channel estimationfor coherent demodulation of downlink physical channels (e.g., PDSCH,PDCCH and PBH) and uplink physical channels (e.g., PUSCH and PUCCH). TheDM-RS may be located early in the transmission (e.g., front-loadedDM-RS) and may enable the receiver to obtain the channel estimate earlyand reduce the latency. The time-domain structure of the DM-RS (e.g.,symbols wherein the DM-RS are located in a slot) may be based ondifferent mapping types.

The Phase Tracking Reference Signals (PT-RSs) enables tracking andcompensation of phase variations across the transmission duration. Thephase variations may be, for example, due to oscillator phase noise. Theoscillator phase noise may become more sever in higher frequencies(e.g., mmWave frequency bands). The base station may configure the PT-RSfor uplink and/or downlink. The PT-RS configuration parameters mayindicate frequency and time density of PT-RS, maximum number of ports(e.g., uplink ports), resource element offset, configuration of uplinkPT-RS without transform precoder (e.g., CP-OFDM) or with transformprecoder (e.g., DFT-s-OFDM), etc. The subcarrier number and/or resourceblocks used for PT-RS transmission may be based on the C-RNTI of thewireless device to reduce risk of collisions between PT-RSs of wirelessdevices scheduled on overlapping frequency domain resources.

FIG. 13B shows example time and frequency structure of CSI-RSs and theirassociation with beams in accordance with several of various embodimentsof the present disclosure. A beam of the L beams shown in FIG. 13B maybe associated with a corresponding CSI-RS resource. The base station maytransmit the CSI-RSs using the configured CSI-RS resources and a UE maymeasure the CSI-RSs (e.g., received signal received power (RSRP) of theCSI-RSs) and report the CSI-RS measurements to the base station based ona reporting configuration. For example, the base station may determineone or more transmission configuration indication (TCI) states and mayindicate the one or more TCI states to the UE (e.g., using RRCsignaling, a MAC CE and/or a DCI). Based on the one or more TCI statesindicated to the UE, the UE may determine a downlink receive beam andreceive downlink transmissions using the receive beam. In case of a beamcorrespondence, the UE may determine a spatial domain filter of atransmit beam based on spatial domain filter of a corresponding receivebeam. Otherwise, the UE may perform an uplink beam selection procedureto determine the spatial domain filter of the transmit beam. The UE maytransmit one or more SRSs using the SRS resources configured for the UEand the base station may measure the SRSs and determine/select thetransmit beam for the UE based the SRS measurements. The base stationmay indicate the selected beam to the UE. The CSI-RS resources shown inFIG. 13B may be for one UE. The base station may configure differentCSI-RS resources associated with a given beam for different UEs by usingfrequency division multiplexing.

A base station and a wireless device may perform beam managementprocedures to establish beam pairs (e.g., transmit and receive beams)that jointly provide good connectivity. For example, in the downlinkdirection, the UE may perform measurements for a beam pair and estimatechannel quality for a transmit beam by the base station (or atransmission reception point (TRP) more generally) and the receive beamby the UE. The UE may transmit a report indicating beam pair qualityparameters. The report may comprise one or more parameters indicatingone or more beams (e.g., a beam index, an identifier of reference signalassociated with a beam, etc.), one or more measurement parameters (e.g.,RSRP), a precoding matrix indicator (PMI), a channel quality indicator(CQI), and/or a rank indicator (RI).

FIG. 14A, FIG. 14B and FIG. 14C show example beam management processes(referred to as P1, P2 and P3, respectively) in accordance with severalof various embodiments of the present disclosure. The P1 process shownin FIG. 14A may enable, based on UE measurements, selection of a basestation (or TRP more generally) transmit beam and/or a wireless devicereceive beam. The TRP may perform a beam sweeping procedure where theTRP may sequentially transmit reference signals (e.g., SSB and/orCSI-RS) on a set of beams and the UE may select a beam from the set ofbeams and may report the selected beam to the TRP. The P2 procedure asshown in FIG. 14B may be a beam refinement procedure. The selection ofthe TRP transmit beam and the UE receive beam may be regularlyreevaluated due to movements and/or rotations of the UE or movement ofother objects. In an example, the base station may perform the beamsweeping procedure over a smaller set of beams and the UE may select thebest beam over the smaller set. In an example, the beam shape may benarrower compared to beam selected based on the P1 procedure. Using theP3 procedure as shown in FIG. 14C, the TRP may fix its transmit beam andthe UE may refine its receive beam.

A wireless device may receive one or more messages from a base station.The one or more messages may comprise one or more RRC messages. The oneor more messages may comprise configuration parameters of a plurality ofcells for the wireless device. The plurality of cells may comprise aprimary cell and one or more secondary cells. For example, the pluralityof cells may be provided by a base station and the wireless device maycommunicate with the base station using the plurality of cells. Forexample, the plurality of cells may be provided by multiple base station(e.g., in case of dual and/or multi-connectivity). The wireless devicemay communicate with a first base station, of the multiple basestations, using one or more first cells of the plurality of cells. Thewireless device may communicate with a second base station of themultiple base stations using one or more second cells of the pluralityof cells.

The one or more messages may comprise configuration parameters used forprocesses in physical, MAC, RLC, PCDP, SDAP, and/or RRC layers of thewireless device. For example, the configuration parameters may includevalues of timers used in physical, MAC, RLC, PCDP, SDAP, and/or RRClayers. For example, the configuration parameters may include parametersfor configurating different channels (e.g., physical layer channel,logical channels, RLC channels, etc.) and/or signals (e.g., CSI-RS, SRS,etc.).

Upon starting a timer, the timer may start running until the timer isstopped or until the timer expires. A timer may be restarted if it isrunning. A timer may be started if it is not running (e.g., after thetimer is stopped or after the timer expires). A timer may be configuredwith or may be associated with a value (e.g., an initial value). Thetimer may be started or restarted with the value of the timer. The valueof the timer may indicate a time duration that the timer may be runningupon being started or restarted and until the timer expires. Theduration of a timer may not be updated until the timer is stopped orexpires (e.g., due to BWP switching). This specification may disclose aprocess that includes one or more timers. The one or more timers may beimplemented in multiple ways. For example, a timer may be used by thewireless device and/or base station to determine a time window [t1, t2],wherein the timer is started at time t1 and expires at time t2 and thewireless device and/or the base station may be interested in and/ormonitor the time window [t1, t2], for example to receive a specificsignaling. Other examples of implementation of a timer may be provided.

FIG. 15 shows example components of a wireless device and a base stationthat are in communication via an air interface in accordance withseveral of various embodiments of the present disclosure. The wirelessdevice 1502 may communicate with the base station 1542 over the airinterface 1532. The wireless device 1502 may include a plurality ofantennas. The base station 1542 may include a plurality of antennas. Theplurality of antennas at the wireless device 1502 and/or the basestation 1542 enables different types of multiple antenna techniques suchas beamforming, single-user and/or multi-user MIMO, etc.

The wireless device 1502 and the base station 1542 may have one or moreof a plurality of modules/blocks, for example RF front end (e.g., RFfront end 1530 at the wireless device 1502 and RF front end 1570 at thebase station 1542), Data Processing System (e.g., Data Processing System1524 at the wireless device 1502 and Data Processing System 1564 at thebase station 1542), Memory (e.g., Memory 1512 at the wireless device1502 and Memory 1542 at the base station 1542). Additionally, thewireless device 1502 and the base station 1542 may have othermodules/blocks such as GPS (e.g., GPS 1514 at the wireless device 1502and GPS 1554 at the base station 1542).

An RF front end module/block may include circuitry between antennas anda Data Processing System for proper conversion of signals between thesetwo modules/blocks. An RF front end may include one or more filters(e.g., Filter(s) 1526 at RF front end 1530 or Filter(s) 1566 at the RFfront end 1570), one or more amplifiers (e.g., Amplifier(s) 1528 at theRF front end 1530 and Amplifier(s) 1568 at the RF front end 1570). TheAmplifier(s) may comprise power amplifier(s) for transmission andlow-noise amplifier(s) (LNA(s)) for reception.

The Data Processing System 1524 and the Data Processing System 1564 mayprocess the data to be transmitted or the received signals byimplementing functions at different layers of the protocol stack such asPHY, MAC, RLC, etc. Example PHY layer functions that may be implementedby the Data Processing System 1524 and/or 1564 may include forward errorcorrection, interleaving, rate matching, modulation, precoding, resourcemapping, MIMO processing, etc. Similarly, one or more functions of theMAC layer, RLC layer and/or other layers may be implemented by the DataProcessing System 1524 and/or the Data Processing System 1564. One ormore processes described in the present disclosure may be implemented bythe Data Processing System 1524 and/or the Data Processing System 1564.A Data Processing System may include an RF module (RF module 1516 at theData Processing System 1524 and RF module 1556 at the Data ProcessingSystem 1564) and/or a TX/RX processor (e.g., TX/RX processor 1518 at theData Processing System 1524 and TX/RX processor 1558 at the DataProcessing System 1566) and/or a central processing unit (CPU) (e.g.,CPU 1520 at the Data Processing System 1524 and CPU 1560 at the DataProcessing System 1564) and/or a graphical processing unit (GPU) (e.g.,GPU 1522 at the Data Processing System 1524 and GPU 1562 at the DataProcessing System 1564).

The Memory 1512 may have interfaces with the Data Processing System 1524and the Memory 1552 may have interfaces with Data Processing System1564, respectively. The Memory 1512 or the Memory 1552 may includenon-transitory computer readable mediums (e.g., Storage Medium 1510 atthe Memory 1512 and Storage Medium 1550 at the Memory 1552) that maystore software code or instructions that may be executed by the DataProcessing System 1524 and Data Processing System 1564, respectively, toimplement the processes described in the present disclosure. The Memory1512 or the Memory 1552 may include random-access memory (RAM) (e.g.,RAM 1506 at the Memory 1512 or RAM 1546 at the Memory 1552) or read-onlymemory (ROM) (e.g., ROM 1508 at the Memory 1512 or ROM 1548 at theMemory 1552) to store data and/or software codes.

The Data Processing System 1524 and/or the Data Processing System 1564may be connected to other components such as a GPS module 1514 and a GPSmodule 1554, respectively, wherein the GPS module 1514 and a GPS module1554 may enable delivery of location information of the wireless device1502 to the Data Processing System 1524 and location information of thebase station 1542 to the Data Processing System 1564. One or more otherperipheral components (e.g., Peripheral Component(s) 1504 or PeripheralComponent(s) 1544) may be configured and connected to the dataProcessing System 1524 and data Processing System 1564, respectively.

In example embodiments, a wireless device may be configured withparameters and/or configuration arrangements. For example, theconfiguration of the wireless device with parameters and/orconfiguration arrangements may be based on one or more control messagesthat may be used to configure the wireless device to implement processesand/or actions. The wireless device may be configured with theparameters and/or the configuration arrangements regardless of thewireless device being in operation or not in operation. For example,software, firmware, memory, hardware and/or a combination thereof and/oralike may be configured in a wireless device regardless of the wirelessdevice being in operation or not operation. The configured parametersand/or settings may influence the actions and/or processes performed bythe wireless device when in operation.

In example embodiments, a wireless device may receive one or moremessage comprising configuration parameters. For example, the one ormore messages may comprise radio resource control (RRC) messages. Aparameter of the configuration parameters may be in at least one of theone or more messages. The one or more messages may comprise informationelement (IEs). An information element may be a structural element thatincludes single or multiple fields. The fields in an IE may beindividual contents of the IE. The terms configuration parameter, IE andfield may be used equally in this disclosure. The IEs may be implementedusing a nested structure, wherein an IE may include one or more otherIEs and an IE of the one or more other IEs may include one or moreadditional IEs. With this structure, a parent IE contains all theoffspring IEs as well. For example, a first IE containing a second IE,the second IE containing a third IE, and the third IE containing afourth IE may imply that the first IE contains the third IE and thefourth IE.

In an example, a wireless device may receive one or more RRC messagescomprising configuration parameters of downlink semi-PersistentScheduling (SPS). The DL SPS configuration may be per Serving Celland/or per BWP. In some examples, the base station may activate and/ordeactivate/release the DL SPS and the activation or thedeactivation/release of DL SPS may be independent among the ServingCells. For the DL SPS, a wireless device may receive a DL assignment byPDCCH, which may be stored or may be cleared based on L1 signallingindicating SPS activation or deactivation.

In an example, the wireless device may receive RRC configurationparameters comprising: cs-RNTI: CS-RNTI for activation, deactivation,and retransmission; nrofHARQ-Processes: the number of configured HARQprocesses for SPS; and periodicity: periodicity of configured downlinkassignment for SPS. When SPS is released by upper layers, thecorresponding configurations may be released.

In an example, after a downlink assignment is configured for SPS, theMAC entity may consider sequentially that the Nth downlink assignmentoccurs in the slot for which:

(numberOfSlotsPerFrame×SFN+slot number in theframe)=[(numberOfSlotsPerFrame×SFN(start time)+slot(starttime))+N×periodicity×numberOfSlotsPerFrame/10]modulo(1024×numberOfSlotsPerFrame)

where SFN(start time) and slot(start time) may be the SFN and slot,respectively, of the first transmission of PDSCH where the configureddownlink assignment was (re-)initialized.

In an example, the IE SPS-Config may be used to configure downlinksemi-persistent transmission. Downlink SPS may be configured on theSpCell as well as on SCells. The IE SPS-Config may comprise one or moreof a mcs-Table parameter indicating a MCS table the UE may use for DLSPS; an n1PUCCH-AN parameter indicating a HARQ resource for PUCCH for DLSPS, a nrofHARQ-Processes parameter indicating a number of configuredHARQ processes for SPS DL; and a periodicity parameter indicating aperiodicity for DL SPS.

In an example, a UE may be expected to provide HARQ-ACK information inresponse to a SPS PDSCH release after N symbols from the last symbol ofa PDCCH providing the SPS PDSCH release, where N may be based on UEprocessing capability and/or numerology (e.g., subcarrier spacing (SCS))of PDCCH reception. For example, for a UE processing capability 1 andfor the SCS of the PDCCH reception, N may be 10 for SCS of 15 kHz, Nmany be 12 for SCS of 30 kHz, N may be 22 for SCS of 60 kHz, and N maybe 25 for SCS of 120 kHz. For a UE with capability 2 in FR1 and for theSCS of the PDCCH reception, N may be 5 for SCS of 15 kHz, N may be 5.5for SCS of 30 kHz, and N may be 11 for SCS of 60 kHz.

In an example, if a UE receives a PDSCH without receiving acorresponding PDCCH, or if the UE receives a PDCCH indicating a SPSPDSCH release, the UE may generate a corresponding HARQ-ACK informationbit. In an example, if a UE is not providedPDSCH-CodeBlockGroupTransmission, the UE may generate a HARQ-ACKinformation bit per transport block.

For a HARQ-ACK information bit, a UE may generate an ACK if the UEdetects a DCI format 1_0 that provides a SPS PDSCH release or correctlydecodes a transport block, and the generates a NACK if the UE does notcorrectly decode the transport block.

In an example, a UE may be provided PDSCH-CodeBlockGroupTransmission fora serving cell. The UE may receive a PDSCH scheduled by DCI format 1_1,that includes code block groups (CBGs) of a transport block. The UE mayalso be provided maxCodeBlockGroupsPerTransportBlock indicating amaximum number of CBGs for generating respective HARQ-ACK informationbits for a transport block reception for the serving cell.

For a number of C code blocks (CBs) in a transport block, the UE maydetermine a number of CBGs M and may determine a number of HARQ-ACK bitsfor the transport block M. The UE may generate an ACK for the HARQ-ACKinformation bit of a CBG if the UE correctly received all code blocks ofthe CBG and generates a NACK for the HARQ-ACK information bit of a CBGif the UE incorrectly received at least one code block of the CBG. Ifthe UE receives two transport blocks, the UE may concatenate theHARQ-ACK information bits for CBGs of the second transport block afterthe HARQ-ACK information bits for CBGs of the first transport block.

In an example, for DCI format 10, the PDSCH-to-HARQ_feedback timingindicator field values may map to {1, 2, 3, 4, 5, 6, 7, 8}. For DCIformat 1_1, if present, the PDSCH-to-HARQ_feedback timing indicatorfield values may map to values for a set of number of slots provided bythe RRC configured parameter dl-DataToUL-ACK.

In an example, for a SPS PDSCH reception ending in slot n, the UE maytransmit the PUCCH in slot n+k where k may be provided by thePDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0 or, ifpresent, in DCI format 1_1 activating the SPS PDSCH reception.

In an example, if the UE detects a DCI format 1_1 that does not includea PDSCH-to-HARQ_feedback timing indicator field and schedules a PDSCHreception or activates a SPS PDSCH reception ending in slot n, the UEmay provide corresponding HARQ-ACK information in a PUCCH transmissionwithin slot n+k where k may be provided by dl-DataToUL-ACK.

With reference to slots for PUCCH transmissions, if the UE detects a DCIformat 1_0 or a DCI format 1_1 scheduling a PDSCH reception ending inslot n or if the UE detects a DCI format 1_0 indicating a SPS PDSCHrelease through a PDCCH reception ending in slot n, the UE may providecorresponding HARQ-ACK information in a PUCCH transmission within slotn+k, where k is a number of slots and is indicated by thePDSCH-to-HARQ_feedback timing indicator field in the DCI format, ifpresent, or provided by dl-DataToUL-ACK. K=0 may correspond to the lastslot of the PUCCH transmission that overlaps with the PDSCH reception orwith the PDCCH reception in case of SPS PDSCH release.

In an example, for a PUCCH transmission with HARQ-ACK information, a UEmay determine a PUCCH resource after determining a set of PUCCHresources for O_(UCI) HARQ-ACK information bits. The PUCCH resourcedetermination may be based on a PUCCH resource indicator field in a lastDCI format 1_0 or DCI format 1_1, among the DCI formats 1_0 or DCIformats 1_1 that have a value of a PDSCH-to-HARQ_feedback timingindicator field indicating a same slot for the PUCCH transmission, thatthe UE detects and for which the UE transmits corresponding HARQ-ACKinformation in the PUCCH where, for PUCCH resource determination,detected DCI formats may be first indexed in an ascending order acrossserving cells indexes for a same PDCCH monitoring occasion and are thenindexed in an ascending order across PDCCH monitoring occasion indexes.In an example, the PUCCH resource indicator field values may map tovalues of a set of PUCCH resource indexes provided by resourceList forPUCCH resources from a set of PUCCH resources provided byPUCCH-ResourceSet with a maximum of eight PUCCH resources.

In an example, if a UE transmits HARQ-ACK information corresponding onlyto a PDSCH reception without a corresponding PDCCH, a PUCCH resource forcorresponding PUCCH transmission with HARQ-ACK information may beprovided by n1PUCCH-AN.

In an example, the DCI format 1_0 may be used for the scheduling ofPDSCH in one DL cell. The following information may be transmitted bymeans of the DCI format 1_0 with CRC scrambled by C-RNTI or CS-RNTI orMCS-C-RNTI: Identifier for DCI formats—1 bit (the value of this bitfield may be set to 1, indicating a DL DCI format); Frequency domainresource assignment—┌log₂(N_(RB) ^(DL,BWP)(N_(RB) ^(DL,BWP)+1)/2┐ bits;Time domain resource assignment—4 bits; VRB-to-PRB mapping—1 bit;Modulation and coding scheme—5 bits; New data indicator—1 bit;Redundancy version—2 bits; HARQ process number—4 bits; Downlinkassignment index—2 bits as counter DAI; TPC command for scheduledPUCCH—2 bits; PUCCH resource indicator—3 bits; PDSCH-to-HARQ_feedbacktiming indicator—3 bits.

In an example, DCI format 1_1 may be used for the scheduling of PDSCH inone cell. The following information may be transmitted by means of theDCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:Identifier for DCI formats—1 bits (The value of this bit field is alwaysset to 1, indicating a DL DCI format); Carrier indicator—0 or 3 bits;Bandwidth part indicator—0, 1 or 2 bits as determined by the number ofDL BWPs n_(BWP,RRC) configured by higher layers, excluding the initialDL bandwidth part; Frequency domain resource assignment; Time domainresource assignment—0, 1, 2, 3, or 4 bits; VRB-to-PRB mapping—0 or 1bit; PRB bundling size indicator—0 bit if the higher layer parameterprb-BundlingType is not configured or is set to ‘static’, or 1 bit ifthe higher layer parameter prb-BundlingType is set to ‘dynamic’; Ratematching indicator—0, 1, or 2 bits according to higher layer parametersrateMatchPatternGroup1 and rateMatchPatternGroup2, where the MSB may beused to indicate rateMatchPatternGroup1 and the LSB may be used toindicate rateMatchPatternGroup2 when there are two groups; ZP CSI-RStrigger—0, 1, or 2 bits; For transport block 1: Modulation and codingscheme—5 bits, New data indicator—1 bit, Redundancy version—2 bits, Fortransport block 2 (present if maxNrofCodeWordsScheduledByDCI equals 2):Modulation and coding scheme—5 bits, New data indicator—1 bit,Redundancyversion—2 bits; HARQ process number—4 bits; Downlink assignment index;TPC command for scheduled PUCCH—2 bits; PUCCH resource indicator—3 bits;PDSCH-to-HARQ_feedback timing indicator—0, 1, 2, or 3 bits; Transmissionconfiguration indication—0 bit if higher layer parametertci-PresentInDCI is not enabled; otherwise 3 bits; SRS request—2 bits;CBG transmission information (CBGTI)—0 bit if higher layer parametercodeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4,6, or 8 bits, determined by the higher layer parametersmaxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCIfor the PDSCH; CBG flushing out information (CBGFI)—1 bit if higherlayer parameter codeBlockGroupFlushIndicator is configured as “TRUE”, 0bit otherwise; DMRS sequence initialization—1 bit.

In an example, a wireless device may receive configuration parameters ofa plurality of DL SPS configurations for a BWP of a serving cell. Thewireless device may be configured with separate RRC parameters fordifferent DL SPS configurations for a given BWP of a serving cell. In anexample, some parameters may be common among different configured grantconfigurations.

In an example, different DL SPS configurations for a given BWP of aserving cell may be separately activated. In an example, a DCI mayjointly activate two or more DL SPS configurations. In an example,different DL SPS configurations for a given BWP of a serving cell may beseparately released/deactivated. In an example, a DCI may jointlydeactivate/release two or more DL SPS configurations.

In an example, M<=4 bits indication in a Release/deactivation DCI may beused for indicating which DL SPS configuration(s) is/are released. Theassociation between each state indicated by the indication and the DLSPS configuration(s) may be configurable by RRC. In an example, up to 2Mstates may be configurable by RRC, where each of the states may bemapped to a single or multiple DL SPS configurations to be released. Inan example, in case of no RRC configured state(s), separate release maybe used where the release corresponds to the DL SPS configuration indexindicated by the indication. In an example, for activation and releaseof DL SPS configuration, same field(s) may be used in a DCI format.

In an example, DCI format 10, DCI format 1_1 and/or a new DCI format maybe used for scheduling PDSCH for DL SPS activation. In an example, DCIformat 1_0, DCI format 1_1 and/or a new DCI format may be used for DLSPS deactivation/release.

In an example, M (M<=4) least significant bits of HARQ Process Number(HPN) field in DCI format 1_0 with CRC scrambled by CS-RNTI may be usedto indicate which configuration is to be activated and whichconfiguration(s) is/are to be released. In an example, (M<=4) leastsignificant bits of HPN field in DCI format 1_1 with CRC scrambled byCS-RNTI may be used to indicate which configuration is to be activated.In an example, M (M<=4) least significant bits of HPN field in DCIformat 1_1 with CRC scrambled by CS-RNTI may be used to indicate whichconfiguration(s) are to be released. In an example, the M for activation(e.g., Ma) and M for deactivation/release (e.g., Mr) may be different.

In an example, at least HPN field in a new DCI format may be used toindicate which configuration is to be activated and/or whichconfiguration(s) is/are to be released. In an example, other field(s)may be used with or in place of the HPN field if the number of bits forHPN field is smaller than M.

In an example, a UE may use a plurality of HARQ feedback codebooks forsupporting different service types.

In an example, multiple PUCCHs for HARQ-ACK within a slot may beconfigured for a UE. The multiple PUCCHs within a slot may be used forsimultaneous HARQ feedback codebooks for different service types. Insome example, sub-slot based HARQ feedback procedures may be used. Insome examples, different PDSCHs may be grouped and HATRQ feedback forPDSCHs in the same group may be transmitted using the same HARQ feedbackcodebook. In some examples, Codebook-less HARQ feedback may be used.

When at least two HARQ-ACK codebooks are simultaneously constructed forsupporting different service types for a UE, a HARQ-ACK codebook may beidentified based on some PHY indications/properties.

In an example, a sub-slot based HARQ feedback procedure may be used forsupporting multiple PUCCHs for HARQ feedback and for constructingmultiple HARQ feedback codebooks within a slot. An UL slot may compriseof a number of sub-slots. A transmitted PUCCH carrying HARQ feedback maystart in a sub-slot and PDSCH transmission may not be subject tosub-slot restrictions. Number or length of UL sub-slots in a slot may beUE-specifically and semi-statically configured. In an example, there maybe a limit on number of PUCCH transmissions carrying HARQ-ACKs in aslot. The PDSCH to HARQ feedback timing field in a DCI scheduling PDSCHmay be in unit of sub-slots. In an example, for sub-slot-based HARQfeedback procedure, timing between PDSCH and HARQ feedback may be thenumber of sub-slots from the sub-slot containing the end of PDSCH to thesub-slot containing the start of PUCCH. The UL numerology (e.g., PUCCHnumerology) may be used to define the sub-slot grid forPDSCH-to-sub-slot association. For sub-slot based HARQ feedbackprocedure, the starting symbol of a PUCCH resource may be defined withrespect to the first symbol of sub-slot. For a given sub-slotconfiguration, a UE can be configured with PUCCH resource set(s).

In an example, when at least two HARQ-ACK codebooks are simultaneouslyconstructed for supporting different service types for a UE, the PHYidentification for identifying a HARQ-ACK codebook may be based on atleast one of DCI format, RNTI, explicit indication in DCI (e.g., basedon a value of a field in the DCI), CORESET/search space, etc.

In an example, when at least two HARQ-ACK codebooks are simultaneouslyconstructed for supporting different service types for a UE, one or moreof the following parameters in PUCCH configuration may be separatelyconfigured for different HARQ-ACK codebooks: K1 (e.g., PDSCH to HARQfeedback timing) granularity, K1 set, PUCCH resource set, MaxCoderate,simultaneousHARQ-ACK-CSI, nrofSlots, power control parameters, timedomain resource allocation (TDRA) table, HARQ feedback codebook type.

In an example, when at least two HARQ feedback codebooks aresimultaneously constructed for supporting different service types for aUE, the PHY identification of HARQ-ACK codebook may be used to determinethe priority of the HARQ-ACK codebook for collision handling.

In an example, when at least two HARQ feedback codebooks aresimultaneously constructed for supporting different service types for aUE, in case of SPS PDSCH, one or more of the following may be used foridentifying a HARQ-ACK codebook: SPS PDSCH configurations, the DCIactivating the SPS PDSCH, the CORESET where the activating DCI isreceived.

In an example, at least one sub-slot configuration for PUCCH may beUE-specifically configured to a UE. At least the following two sub-slotconfigurations for PUCCH may be used: “2-symbol*7” and “7-symbol*2”. Insome example, other configurable sub-slot configurations, e.g. 4, 14sub-slots in a slot may be used.

In an example, when at least two HARQ feedback codebooks aresimultaneously constructed for supporting different service types for aUE, following can be separately configured for different HARQ-ACKcodebooks: PUCCH-SpatialRelationInfo, sub-slot configuration (e.g.,applied for the sub-slot-based HARQ-ACK codebook). In some example, whenthere are at least two HARQ-ACK codebooks configured with sub-slots, thesame sub-slot configurations may be used. In some example, when thereare at least two HARQ-ACK codebooks configured with sub-slots, differentsub-slot configurations may be used.

In an example, when at least two HARQ feedback codebooks aresimultaneously constructed for supporting different service types for aUE, the PHY identification for identifying a HARQ feedback codebook fordynamically scheduled PDSCH may be based on RNTI or based on explicitindication in DCI. When at least two HARQ feedback codebooks aresimultaneously constructed for supporting different service types for aUE, the PHY identification for identifying a HARQ feedback codebook forSPS PDSCH may be based on SPS PDSCH configurations (e.g. explicitindicator, periodicity, PDSCH duration, etc.) or based on the DCI formatactivating the SPS PDSCH. The PHY identification of HARQ feedbackcodebook may be used to determine the priority of the HARQ-ACK codebookfor collision handling.

In an example, a 2-level priority of HARQ feedback for dynamicallyscheduled PDSCH and SPS PDSCH and ACK for SPS PDSCH release may be used.An explicit indication (e.g., as a new RRC parameter) in a SPS PDSCHconfiguration may provide mapping to corresponding HARQ-ACK codebook forSPS PDSCH and ACK for SPS PDSCH release.

Example embodiments may operate considering different types oftraffic/service types including enhanced mobile broadband (eMBB)traffic/service type and ultra-reliable low-latency communications(URLLC) traffic/service types. The eMBB traffic/service type may berelated to high data rate applications where latency and reliabilityrequirements may not be as strict as the data rate requirements. TheURLLC applications may have strict requirements on latency andreliability and may require comparatively lower data rates than the eMBBtraffic/service type.

A wireless device may transmit an acknowledgement in response toreceiving a DCI indicating release/deactivation of a DL SPSconfiguration. The timing of the acknowledgement may be based on a valueof field in the release/deactivation DCI (e.g., a value of thePDSCH-to-HARQ-feedback-timing field), a timing of the reception of thePDCCH carrying the release/deactivation DCI and a numerology of anuplink channel carrying the acknowledgement (e.g., numerology of PUCCH).For example, the numerology of the uplink channel carrying theacknowledgement may determine a subslot duration, wherein the subslotcomprise one or more symbols. The PDSCH-to-HARQ-feedback-timing field inthe release/deactivation DCI may indicate the number of the subslotsfrom the timing that the PDCCH carrying the release/deactivation DCI isreceived until the timing that the acknowledgement is transmitted.

For deactivation of a DL SPS configurations, the base station maytransmit a release/deactivation DCI indicating that the DL SPSconfiguration is deactivated. It is important for the wireless device toacknowledge the receipt of the release/deactivation DCI so that the basestation determines that the wireless device correctly received the DCIand that the wireless device deactivated resources corresponding to theDL SPS configurations. When a group of DL SPS configurations are jointlydeactivated/released by a single deactivation/release DCI, existingacknowledgement processes or HARQ feedback codebook determinationprocesses lead to inefficient DL SPS operation. There is a need toenhance the existing DL SPS deactivation/release mechanisms when a groupof DL SPS configurations are jointly released/deactivated. Exampleembodiments enhance the DL SPS deactivation/release mechanisms when agroup of DL SPS configurations are jointly released/deactivated.

In an example embodiment as shown in FIG. 16 , a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise one or more RRC messages. The one ormore messages may comprise configuration parameters of a downlinksemi-persistent scheduling (DL SPS) configuration. The DL SPSconfiguration may comprise a first parameter indicating a periodicity, asecond parameter indicating a number of HARQ processes associated withthe DL SPS configurations, a third parameter indicating a HARQ feedbackcodebook and/or a priority and/or a traffic/service type and otherparameters. The wireless device may receive an activation DCI indicatingactivation of a plurality of resources for the DL SPS configuration. Inan example, the activation DCI may overwrite the HARQ feedback codebookindicated by the third parameter or may indicate the same HARQ feedbackcodebook configured by the third parameter. Based on the configurationof the third parameter, the wireless device may transmit HARQ feedback(e.g., ACK or NACK) for DL transport blocks transmitted via the DL SPSresources using the HARQ feedback codebook corresponding to the DL SPSconfiguration (e.g., as configured by third RRC parameter or asindicated/overwritten by the activation DCI). The wireless device mayreceive a release/deactivation DCI indication release/deactivation ofthe DL SPS configuration. The wireless device may transmit anacknowledgement based on the receiving the release/deactivation DCI. Thewireless device may transmit the acknowledgement based on the HARQfeedback codebook associated with the DL SPS configuration.

In an example embodiment as shown in FIG. 17 , a wireless device mayreceive configuration parameters of a plurality of DL SPS configurations(e.g., 1st DL SPS configuration through Nth DL SPS configuration). Thewireless device may receive one or more activation DCIs (e.g., Nactivation DCIs) indicating activation of the N DL SPS configurations.The wireless device may jointly release/deactivate the N DL SPSconfigurations based on a single release/deactivation DCI indicatingjoint release/deactivation of the N DL SPS configurations. Therelease/deactivation DCI may comprise a field (e.g., a HARQ processnumber (HPN) field) comprising first bits wherein one or more secondbits of the first bits may indicate the N DL SPS configurations (e.g., agroup identifier of the N DL SPS configurations). In an example,configuration parameters of the N DL SPS configurations may comprise thegroup identifier.

In an example embodiment as shown in FIG. 18 , a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise RRC messages. The one or more messagesmay comprise first configuration parameters of a first downlinksemi-persistent scheduling (DL SPS) configuration and secondconfiguration parameters of a second DL SPS configuration. In anexample, the first DL SPS configuration and the second DL SPSconfiguration may be for a cell (e.g., for a BWP of a cell). In anexample, the first DL SPS configuration may be for a first BWP of a celland the second DL SPS configuration may be for a second BWP of the cell.In an example, the first DLS SPS configuration and the second DL SPSconfiguration may be for different cells. The first DL SPS configurationparameters may indicate a first periodicity and/or a first number ofHARQ processes and/or a first configuration index and/or a first group(e.g., group of DL SPS configurations) identifier, etc. The second DLSPS configuration parameters may indicate a second periodicity and/or asecond number of HARQ processes and/or a second configuration indexand/or a second group (e.g., group of DL SPS configurations) identifier,etc.

The wireless device may receive a downlink control informationindicating release/deactivation of the first DL SPS configuration andrelease/deactivation of the second DL SPS configuration. The downlinkcontrol information may jointly indicate release/deactivation of thefirst DL SPS configuration and the second DL SPS configuration. In anexample, the downlink control information may comprise a field (e.g., aHARQ process number field) comprising first bits, wherein one or moresecond bits of the first bits may indicate the first DL SPSconfiguration and the second DL SPS configuration. In an example, anumber of the one or more second bits may be a second number and the oneor more second bits may be second number least significant bits of thefirst bits. In an example, the one or more second bits may indicate agroup identifier of a group comprising a plurality of DL SPSconfigurations comprising the first DL SPS and the second DL SPS. Thefirst configuration parameters of the first DL SPS may comprise thegroup identifier and the second configuration parameters of the secondDL SPS may indicate the group identifier.

The first DL SPS configuration may be associated with a first HARQfeedback codebook and the second DL SPS configuration may be associatedwith a second HARQ feedback group. In an example, the first DL SPSconfiguration parameters may comprise a first parameter indicating thefirst HARQ feedback codebook and the second DL SPS configurationparameters may comprise a second parameter indicating the second HARQfeedback codebook. In an example, the first parameter may indicate afirst priority and/or a first traffic/service type (e.g., ultra-reliablelow-latency communications (URLLC), enhanced mobile broadband (eMBB),etc.) wherein the first priority and/or the first traffic/service typemay indicate the first HARQ feedback codebook. In an example, the secondparameter may indicate a second priority and/or a second traffic/servicetype (e.g., URLLC, eMBB, etc.) wherein the second priority and/or thesecond traffic/service type may indicate the second HARQ feedbackcodebook.

In an example, the wireless device may receive a first activation DCIindicating activation of a plurality of resources based on the first DLSPS configuration wherein the first activation DCI may indicate thefirst HARQ feedback codebook. In an example, the wireless device maydetermine the first HARQ feedback codebook based on an explicitindication in the first activation DCI or based on one or moreparameters associated with the first activation DCI. For example, a CRCassociated with the first activation DCI may be scrambled with a firstRNTI and the wireless device may determine the first HARQ feedbackcodebook based on the first RNTI. For example, the first RNTI mayindicate a first priority and/or traffic/service type, wherein the firstpriority and/or traffic/service type may indicate the first HARQfeedback codebook. In an example, a value of a field of the firstactivation DCI may indicate the first HARQ feedback codebook. Forexample, a value of a field of the first activation DCI may indicate afirst priority and/or traffic/service type, wherein the first priorityand/or traffic/service type may indicate the first HARQ feedbackcodebook. In an example, a search space/CORESET associated with thefirst activation DCI (e.g., the search space/CORESET in which the firstactivation DCI is received) may indicate the first HARQ feedbackcodebook. For example, a search space/CORESET associated with the firstactivation DCI may indicate a first priority and/or traffic/service typewherein the first priority and/or traffic/service type may indicate thefirst HARQ feedback codebook. In an example, a first format associatedwith the first activation DCI may indicate the first HARQ feedbackcodebook. For example, the first format associated with the firstactivation DCI may indicate a first priority and/or a firsttraffic/service type wherein the first priority and/or traffic/servicetype may indicate the first HARQ feedback codebook.

In an example, the wireless device may receive a second activation DCIindicating activation of a plurality of resources based on the second DLSPS configuration wherein the second activation DCI may indicate thesecond HARQ feedback codebook. In an example, the wireless device maydetermine the second HARQ feedback codebook based on an explicitindication in the second activation DCI or based on one or moreparameters associated with the second activation DCI. For example, a CRCassociated with the second activation DCI may be scrambled with a secondRNTI and the wireless device may determine the second HARQ feedbackcodebook based on the second RNTI. For example, the second RNTI mayindicate a second priority and/or traffic/service type, wherein thesecond priority and/or traffic/service type may indicate the second HARQfeedback codebook. In an example, a value of a field of the secondactivation DCI may indicate the second HARQ feedback codebook. Forexample, a value of a field of the second activation DCI may indicate asecond priority and/or traffic/service type, wherein the second priorityand/or traffic/service type may indicate the second HARQ feedbackcodebook. In an example, a search space/CORESET associated with thesecond activation DCI (e.g., the search space/CORESET in which thesecond activation DCI is received) may indicate the second HARQ feedbackcodebook. For example, a search space/CORESET associated with the secondactivation DCI may indicate a second priority and/or traffic/servicetype wherein the second priority and/or traffic/service type mayindicate the second HARQ feedback codebook. In an example, a secondformat associated with the second activation DCI may indicate the secondHARQ feedback codebook. For example, the second format associated withthe second activation DCI may indicate a second priority and/or a firsttraffic/service type wherein the second priority and/or traffic/servicetype may indicate the first HARQ feedback codebook.

In an example, an activation DCI of a DL SPS configuration (e.g., thefirst activation DCI of the first DL SPS configuration or the secondactivation DCI of the second DL SPS configuration) may indicate a HARQfeedback codebook that may overwrite the HARQ feedback code bookconfigured by the DL SPS configuration parameters. For example, firstconfiguration parameters of the first DL SPS configuration may indicatea HARQ feedback codebook and the first activation DCI indicatingactivation of the first DL SPS may overwrite the configured HARQfeedback codebook and may indicate the first HARQ feedback codebook. Forexample, second configuration parameters of the second DL SPSconfiguration may indicate a HARQ feedback codebook and the secondactivation DCI indicating activation of the second DL SPS may overwritethe configured HARQ feedback codebook and may indicate the second HARQfeedback codebook.

Based on the first DL SPS configuration being associated with the firstHARQ feedback codebook, the wireless device may transmit HARQ feedbackassociated with the downlink transport blocks, received via the first DLSPS resources, based on the first HARQ feedback codebook. The wirelessdevice may transmit ACK/NACK associated with the first DL SPSconfiguration using the first HARQ feedback codebook. The wirelessdevice may create the first HARQ feedback codebook based on ACK/NACK fora plurality of downlink TBs that have the first priority associated withthe first HARQ feedback codebook or are associated with the firsttraffic/service type. Based on the second DL SPS configuration beingassociated with the second HARQ feedback codebook, the wireless devicemay transmit HARQ feedback associated with the downlink transportblocks, received via the second DL SPS resources, based on the secondHARQ feedback codebook. The wireless device may transmit ACK/NACKassociated with the second DL SPS configuration using the second HARQfeedback codebook. The wireless device may create the second HARQfeedback codebook based on ACK/NACK for a plurality of downlink TBs thathave the second priority associated with the second HARQ feedbackcodebook or are associated with the second traffic/service type.

Based on the receiving the downlink control information indicating jointrelease/deactivation of the first DL SPS configuration and the second DLSPS configuration, the wireless device may determine one of the firstHARQ feedback (associated with the first DL SPS configuration) and thesecond HARQ feedback codebook (associated with the second DL SPSconfiguration) based on one or more criteria. The wireless device maytransmit an acknowledgement based on the receiving the downlink controlinformation and based on the determined HARQ feedback codebook.

In an example, the determining the one of the first HARQ feedbackcodebook and the second HARQ feedback codebook may be based onpriorities associated with the first HARQ feedback codebook and thesecond HARQ feedback codebook. In an example, the determining the one ofthe first HARQ feedback codebook and the second HARQ feedback codebookmay be based on priorities associated with the first DL SPSconfiguration and the second DL SPS configuration. For example, thefirst HARQ feedback codebook may be associated with a first priority andthe second HARQ feedback codebook may be associated with a secondpriority. The determining the one of the first HARQ feedback codebookand the second HARQ feedback codebook may be based on the first priorityand the second priority. In an example, the determined HARQ feedbackcodebook may be the first HARQ feedback codebook based on the firstpriority being larger than the second priority.

In an example, the determining the one of the first HARQ feedbackcodebook and the second HARQ feedback codebook may be based onservice/traffic types associated with the first HARQ feedback codebookand the second HARQ feedback codebook. In an example, the determiningthe one of the first HARQ feedback codebook and the second HARQ feedbackcodebook may be based on traffic/service types associated with the firstDL SPS configuration and the second DL SPS configuration. For example,the first HARQ feedback codebook may be associated with a firsttraffic/service type and the second HARQ feedback codebook may beassociated with a second traffic/service type. The determining the oneof the first HARQ feedback codebook and the second HARQ feedbackcodebook may be based on the first traffic/service type and the secondtraffic/service type. In an example, the determined HARQ feedbackcodebook may be the first HARQ feedback codebook based on the firsttraffic/service type being a URLLC traffic/service type and the secondHARQ feedback codebook being an eMBB traffic/service type.

In an example, the determining the one of the first HARQ feedbackcodebook and the second HARQ feedback codebook may be based on types ofthe first HARQ feedback codebook and the second HARQ feedback codebook.In an example, the determining the one of the first HARQ feedbackcodebook and the second HARQ feedback codebook may be based on types ofthe first DL SPS configuration and the second DL SPS configuration. Forexample, the first HARQ feedback codebook may be have a first type andthe second HARQ feedback codebook may have a second type. Thedetermining the one of the first HARQ feedback codebook and the secondHARQ feedback codebook may be based on the first type and the secondtype. In an example, the determined HARQ feedback codebook may be thefirst HARQ feedback codebook based on a first priority of the first typebeing larger than a second priority of the second type. In an example,the first configuration parameters of the DL SPS configuration mayindicate the first type and the second configuration parameters of thesecond DL SPS may indicate the second type.

In an example embodiment as shown in FIG. 19 , a wireless device mayreceive one or more messages comprising configuration parameters. Theone or more messages may comprise RRC messages. The one or more messagesmay comprise configuration parameters of a plurality of DL SPSconfigurations. In an example, the plurality of DL SPS configurationsmay be for a cell (e.g., a BWP of a cell or a plurality of BWPs of acell). In an example, the plurality of DL SPS configurations may be fora plurality of cells (e.g., a plurality of BWPs of a plurality ofcells). Configuration parameters of a DL SPS may indicate periodicityand/or number of HARQ processes and/or configuration index and/or agroup (e.g., group of DL SPS configurations) identifier, etc.

The wireless device may receive a downlink control informationindicating release/deactivation of the plurality of DL SPSconfigurations. The downlink control information may jointly indicaterelease/deactivation of the plurality of DL SPS configurations. In anexample, the downlink control information may comprise a field (e.g., aHARQ process number field) comprising first bits, wherein one or moresecond bits of the first bits may indicate the plurality of DL SPSconfigurations. In an example, a number of the one or more second bitsmay be a second number and the one or more second bits may be secondnumber least significant bits of the first bits. In an example, the oneor more second bits may indicate a group identifier of a groupcomprising the plurality of DL SPS configurations. Configurationparameters of a DL SPS in the plurality of DL SPS configurations maycomprise and/or indicate the group identifier.

The plurality of DL SPS configurations may be associated with aplurality of HARQ feedback codebooks. In an example, configurationparameters of a DL SPS configuration, in the plurality of DL SPSconfigurations, may comprise a parameter indicating a HARQ feedbackcodebook in the plurality of HARQ feedback codebooks. In an example, theparameter may indicate a priority and/or traffic/service type (e.g.,ultra-reliable low-latency communications (URLLC), enhanced mobilebroadband (eMBB), etc.) wherein the priority and/or the traffic/servicetype may indicate the HARQ feedback codebook.

In an example, the wireless device may receive an activation DCIindicating activation of a plurality of resources based on a DL SPSconfiguration, in the plurality of DL SPS configurations, wherein theactivation DCI may indicate a HARQ feedback codebook. In an example, thewireless device may determine the HARQ feedback codebook based on anexplicit indication in the activation DCI or based on one or moreparameters associated with the activation DCI. For example, a CRCassociated with the activation DCI may be scrambled with an RNTI and thewireless device may determine the HARQ feedback codebook based on theRNTI. For example, the RNTI may indicate a priority and/ortraffic/service type, wherein the priority and/or traffic/service typemay indicate the HARQ feedback codebook. In an example, a value of afield of the activation DCI may indicate the HARQ feedback codebook. Forexample, a value of a field of the activation DCI may indicate apriority and/or traffic/service type, wherein the priority and/ortraffic/service type may indicate the HARQ feedback codebook. In anexample, a search space/CORESET associated with the activation DCI(e.g., the search space/CORESET in which the activation DCI is received)may indicate the HARQ feedback codebook. For example, a searchspace/CORESET associated with the activation DCI may indicate a priorityand/or traffic/service type wherein the priority and/or traffic/servicetype may indicate the HARQ feedback codebook. In an example, a formatassociated with the activation DCI may indicate the HARQ feedbackcodebook. For example, the format associated with the activation DCI mayindicate a priority and/or a traffic/service type wherein the priorityand/or traffic/service type may indicate the HARQ feedback codebook.

In an example, an activation DCI of a DL SPS configuration may indicatea HARQ feedback codebook that may overwrite the HARQ feedback code bookconfigured by the DL SPS configuration parameters. For example,configuration parameters of a DL SPS configuration, in the plurality ofDL SPS configurations, may indicate a HARQ feedback codebook and theactivation DCI indicating activation of the DL SPS configuration mayoverwrite the configured HARQ feedback codebook.

Based on the receiving the downlink control information indicating jointrelease/deactivation of the plurality of DL SPS configurations, thewireless device may determine a HARQ feedback of the plurality of HARQfeedback codebooks based on one or more criteria. The wireless devicemay transmit an acknowledgement based on the receiving the downlinkcontrol information (indicating joint release of the plurality of DL SPSconfigurations) and based on the determined HARQ feedback codebook.

In an example, the determining the HARQ feedback codebook may be basedon priorities associated with the plurality of HARQ feedback codebooks.In an example, the determining the HARQ feedback codebook may be basedon priorities associated with the plurality of DL SPS configurations.The determining the HARQ feedback codebook may be based on the priorityof the determined HARQ feedback codebook being the highest priority.

In an example, the determining the HARQ feedback codebook may be basedon service/traffic types associated with the plurality of HARQ feedbackcodebooks. In an example, the determining the HARQ feedback codebook maybe based on traffic/service types associated with the plurality of DLSPS configurations. For example, the determined HARQ feedback codebookmay be associated with a first traffic/service type. In an example, thefirst HARQ feedback codebook may be based on a URLLC traffic/servicetype.

In an example, the determining the HARQ feedback codebook may be basedon types of the plurality of HARQ feedback codebooks. In an example, thedetermining the HARQ feedback codebook may be based on types of theplurality of DL SPS configurations. For example, the determined HARQfeedback codebook may be a HARQ feedback codebook associated withhighest priority. In an example, the configuration parameters of theplurality of DL SPS configuration may indicate the HARQ feedbackcodebook types.

In an example, the determining the HARQ feedback codebook may be basedon a majority of the plurality of HARQ feedback codebooks being thedetermined HARQ feedback codebook. The plurality of DL SPSconfigurations may be associated with different HARQ feedback codebookswith the determined HARQ feedback codebook being the majority HARQfeedback codebook among the plurality of HARQ feedback codebooks.

In an example, the plurality of HARQ feedback codebooks may comprisezero or more of a first HARQ feedback codebook, corresponding to a firstpriority. The plurality of HARQ feedback codebooks may comprise zero ormore of a second HARQ feedback codebook, corresponding to a secondpriority. The first priority of the first HARQ feedback codebook may behigher than the second priority of the second HARQ feedback codebook.The first HARQ feedback codebook may be for a first type oftraffic/service and the second HARQ feedback codebook is for a secondtype of traffic/service. For example, the first type of traffic/servicemay be URLLC and the second type of traffic/service may be eMBB. Thedetermined HARQ feedback codebook may be the first HARQ feedbackcodebook based on at least one of the plurality of HARQ feedbackcodebooks being the first HARQ feedback codebook.

In an example, the plurality of HARQ feedback codebooks may comprise oneor more of a first HARQ feedback codebook, corresponding to a firstpriority. The plurality of HARQ feedback codebooks may comprise one ormore of a second HARQ feedback codebook, corresponding to a secondpriority. The first priority of the first HARQ feedback codebook may behigher than the second priority of the second HARQ feedback codebook.The first HARQ feedback codebook may be for a first type oftraffic/service and the second HARQ feedback codebook is for a secondtype of traffic/service. For example, the first type of traffic/servicemay be URLLC and the second type of traffic/service may be eMBB. Thedetermined HARQ feedback codebook may be the first HARQ feedbackcodebook based on the plurality of HARQ feedback codebooks comprising anequal number of first HARQ feedback codebooks and second HARQ feedbackcodebooks.

In an example, the determined HARQ feedback may be a pre-configuredand/or configured HARQ feedback codebook based on the DCI indicatingrelease/deactivation of a plurality of DL SPS configurations. Theconfiguration parameters may indicate the HARQ feedback codebook to beused by the wireless device for transmission of an acknowledgement whena plurality of DL SPS configurations are jointly deactivated/released.

In an example, based the DCI indicating deactivation/release of aplurality of DL SPS configurations, the wireless device may determine aHARQ feedback codebook associated with one of the DL SPS configurationsbased on a rule. In an example, the rule may be based on a configurationindexes of the plurality of DL SPS configurations. For example, thedetermined HARQ feedback codebook may be the HARQ feedback codebookassociated with the DL SPS configuration with smallest configurationindex. For example, the determined HARQ feedback codebook may be theHARQ feedback codebook associated with the DL SPS configuration withlargest configuration index.

In an example embodiment as shown in FIG. 20 , a wireless device mayreceive one or more messages (e.g., RRC messages) indicatingconfiguration parameters of two DL SPS configurations. The wirelessdevice may receive a DCI indicating deactivation/release of the two DLSPS configurations. The DCI may comprise a field (e.g., HPN field),wherein one or more bits of the field may indicate a plurality of DL SPSconfigurations comprising the two DL SPS configurations. The wirelessdevice may determine that the two DL SPS configurations correspond totwo different HARQ feedback codebooks. In an example, the configurationparameters may indicate HARQ feedback codebooks associated with the twoDL SPS configurations. In an example, an activation DCI, indicatingactivation of a DL SPS configuration of the two DL SPS configurations,may overwrite a configured HARQ feedback codebook and may indicate a newHARQ feedback codebook. Based on the determining that the two DL SPSconfigurations correspond to two different HARQ feedback codebooks, thewireless device may ignore the downlink control information indicatingthe joint release of the two DL SPS configurations.

In an example embodiment, a DCI may indicate joint release/deactivationof a plurality of DL SPS configurations. The plurality of DL SPSconfigurations may be associated with a plurality of HARQ feedbackcodebooks. The wireless device may determine that a subset of DL SPSconfigurations which may be the majority of DL SPS configurationscorrespond to a first HARQ feedback codebook. The wireless device mayrelease/deactivate the subset of the DL SPS configurations correspondingto the first HARQ feedback codebook. The wireless device may transmit anacknowledgement based on the first HARQ feedback codebook. In anexample, the wireless device may not release/deactivate other remainingDL SPS configurations in the plurality of DL SPS configurations.

In an example embodiment as shown in FIG. 21 , a wireless device mayreceive configuration parameters of one or more DL SPS configurations.The one or more DL SPS configurations may correspond to one or morefirst HARQ feedback codebooks. For example, the configuration parametersof the on or more DL SPS configurations may indicate the one or morefirst HARQ feedback codebooks. In an example, a HARQ feedback codebookassociated with a DL SPS configuration, in the one or more DL SPSconfigurations, may be indicated by an activation DCI indicatingactivation of the DL SPS configuration. The wireless device may receivea DCI indicating release/deactivation of the one or more DL SPSconfigurations. The one or more DL SPS configurations may be associatedwith one or more first HARQ feedback codebooks. The DCI indicating thedeactivation/release may indicate a second HARQ feedback codebook (e.g.,based on a value of a field in the deactivation/release DCI and/or anRNTI associated with the deactivation/release DCI and/or a formatassociated with the deactivation/release DCI and/or search space/CORESETassociated with the deactivation/release DCI, etc.). The wireless devicemay transmit an acknowledge based on the second HARQ feedback codebook(e.g., the HARQ feedback codebook indicated by the deactivation/releaseDCI). The wireless device may transmit an acknowledge based on thesecond HARQ feedback codebook (e.g., the HARQ feedback codebookindicated by the deactivation/release DCI) and regardless of the one ormore first HARQ feedback codebooks.

In an example embodiment as shown in FIG. 22 and FIG. 23 , a wirelessdevice may receive first configuration parameters of a first downlinksemi-persistent scheduling configuration and second configurationparameters of a second downlink semi-persistent schedulingconfiguration. The wireless device may receive a DCI indicatingrelease/deactivation of the first downlink semi-persistent schedulingconfiguration and release/deactivation of the second downlinksemi-persistent scheduling configuration. For example, a field in theDCI may indicate joint release/deactivation of the first DL SPS and thesecond DL SPS. The first DL SPS may be associated with a first HARQfeedback codebook (e.g., based on configuration parameters and/or anactivation DCI indicating activation of the first DL SPS). The second DLSPS may be associated with a second HARQ feedback codebook (e.g., basedon configuration parameters and/or an activation DCI indicatingactivation of the second DL SPS). Based on the receiving the DCIindicating joint release/deactivation of the first DL SPS and the secondDL SPS, the wireless device may transmit a first acknowledgement basedon the first HARQ feedback codebook and the wireless device may transmita second acknowledgement based on the second HARQ feedback codebook.

In an example embodiment as shown in FIG. 24 and FIG. 25 , based onreceiving a DCI indicating release/deactivation of a plurality of DL SPSconfigurations, a wireless device may transmit a first acknowledgementusing a first HARQ feedback codebook based on the plurality HARQfeedback codebook comprising the first HARQ feedback codebook and thewireless device may transmit a second acknowledgement using a secondHARQ feedback codebook based on the plurality HARQ feedback codebookcomprising the second HARQ feedback codebook.

A wireless device may transmit a plurality of acknowledgements (e.g.,using a plurality of HARQ feedback codebooks) based on receiving a DCIindicating release/deactivation of a plurality of DL SPS configurationsand based on example embodiments. In an example, the DCI may indicate asingle timing and the plurality acknowledgements may be transmittedbased on the single timing indicated by the DCI. The timing indicated bythe DCI may be in unit of subslot wherein a subslot is one or moresymbols determined based on a numerology of an uplink channel (e.g.,PUCCH). One or more first acknowledgements, of the plurality ofacknowledgements, may be transmitted by a first HARQ feedback codebookand one or more second acknowledgements, of the plurality ofacknowledgements, may be transmitted by a second HARQ feedback codebook.

In an example as shown in FIG. 22 and FIG. 24 , the timing of thetransmission of the one or more first acknowledgements (corresponding tothe first HARQ feedback codebook) and the one or more secondacknowledgements (corresponding to the second HARQ feedback codebook)may be based on a single timing value indicated by therelease/deactivation DCI. In an example, the wireless device maydetermine first timing of the first HARQ feedback codebook based on thetiming value indicated by the release/deactivation DCI and the secondtiming of the second HARQ feedback codebook based on the first timing ofthe first HARQ feedback codebook and an offset. In an example, theoffset may be RRC configured. In an example, the offset may be in termsof a number of subslots wherein a subslot may comprise one or moresymbols based on a numerology of an uplink channel (e.g., PUCCH). In anexample, the offset may be pre-determined. In an example, the offset maybe indicated by the release/deactivation DCI. In an example, the timingof a HARQ feedback codebook corresponding to URLLC traffic/service typemay be earlier than the timing of a second HARQ feedback codebookcorresponding to eMBB.

In an example as shown in FIG. 23 and FIG. 25 , both of one or morefirst acknowledgements (corresponding to the first HARQ feedbackcodebook) and the one or more second acknowledgements (corresponding tothe second HARQ feedback codebook) may be transmitted at the same timing(e.g., same subslot) indicated by the release/deactivation DCI.

In an example embodiment, a wireless device may receive firstconfiguration parameters of a first downlink semi-persistent schedulingconfiguration and second configuration parameters of a second downlinksemi-persistent scheduling configuration. The wireless device mayreceive a downlink control information indicating release/deactivationof the first downlink semi-persistent scheduling configuration andrelease/deactivation of the second downlink semi-persistent schedulingconfiguration, wherein: the first downlink semi-persistent schedulingmay be associated with a first HARQ feedback codebook; and the seconddownlink semi-persistent scheduling may be associated with a second HARQfeedback codebook. The wireless device may determine one of the firstHARQ feedback codebook and the second HARQ feedback codebook based onone or more criteria. The wireless device may transmit anacknowledgement based on the receiving the downlink control informationand based on the determined HARQ feedback codebook.

In an example, the first configuration parameters may comprise a firstparameter indicating a first HARQ feedback codebook; and the secondconfiguration parameters may comprise a second parameter indicating asecond HARQ feedback codebook.

In an example, the wireless device may receive a first downlink controlinformation indicating: scheduling activation of the first downlinksemi-persistent scheduling; and the first HARQ feedback codebook. In anexample, an RNTI associated with the first downlink control informationmay indicate the first HARQ feedback codebook. In an example, the RNTIassociated with the first downlink control information may indicate afirst priority indicating the first HARQ feedback codebook. In anexample, a value of a field of the first downlink control informationmay indicate the first HARQ feedback codebook. In an example, a value ofa field of the first downlink control information may indicate a firstpriority indicating the first HARQ feedback codebook. In an example, asearch space/CORESET associated with the first downlink controlinformation (e.g., a search space/CORESET in which the first downlinkcontrol information is received) may indicate the first HARQ feedbackcodebook. In an example, a search space/CORESET associated with thefirst downlink control information (e.g., a search space/CORESET inwhich the first downlink control information is received) may indicate afirst priority indicating the first HARQ feedback codebook. In anexample, a first format associated with the first downlink controlinformation may indicate the first HARQ feedback codebook. In anexample, a first format associated with the first downlink controlinformation may indicate a first priority indicating the first HARQfeedback codebook.

In an example, the wireless device may receive a second downlink controlinformation indicating: scheduling activation of the second downlinksemi-persistent scheduling; and the second HARQ feedback codebook. In anexample, an RNTI associated with the second downlink control informationmay indicate the second HARQ feedback codebook. In an example, the RNTIassociated with the second downlink control information may indicate asecond priority indicating the second HARQ feedback codebook. In anexample, a value of a field of the second downlink control informationmay indicate the second HARQ feedback codebook. In an example, a valueof a field of the second downlink control information may indicate asecond priority indicating the second HARQ feedback codebook. In anexample, a search space/CORESET associated with the second downlinkcontrol information (e.g., a search space/CORESET in which the seconddownlink control information is received) may indicate the second HARQfeedback codebook. In an example, a search space/CORESET associated withthe second downlink control information (e.g., a search space/CORESET inwhich the second downlink control information is received) may indicatea second priority indicating the second HARQ feedback codebook. In anexample, a second format associated with the second downlink controlinformation may indicate the second HARQ feedback codebook. In anexample, a second format associated with the second downlink controlinformation may indicate a second priority indicating the second HARQfeedback codebook.

In an example, the first downlink control information may indicate thefirst HARQ feedback codebook, wherein the HARQ feedback codebookindicated by the first downlink control information may overwrite a HARQfeedback codebook indicated by a first parameter of the firstconfiguration parameters.

In an example, the second downlink control information may indicate thesecond HARQ feedback codebook, wherein the HARQ feedback codebookindicated by the second downlink control information may overwrite aHARQ feedback codebook indicated by a second parameter of the secondconfiguration parameters.

In an example, the first HARQ feedback codebook may be associated with afirst priority. In an example, the first HARQ feedback may be associatedwith a first traffic/service type.

In an example, the second HARQ feedback codebook may be associated witha second priority. In an example, the second HARQ feedback may beassociated with a second traffic/service type.

In an example, the first HARQ feedback codebook may be associated with afirst priority; the second HARQ feedback codebook may be associated witha second priority; and the determining one of the first HARQ feedbackcodebook and the second HARQ feedback codebook may be based on the firstpriority and the second priority. In an example, the determined HARQfeedback codebook may be the first HARQ feedback based on the firstpriority being larger than the second priority.

In an example, the first HARQ feedback codebook may be associated with afirst traffic/service type; the second HARQ feedback codebook may beassociated with a second traffic/service type; and the determining oneof the first HARQ feedback codebook and the second HARQ feedbackcodebook may be based on the first traffic/service type and the secondtraffic/service type. In an example, the determined HARQ feedbackcodebook may be the first HARQ feedback based on the firsttraffic/service type being URLLC and the second traffic/service typebeing eMBB.

In an example, the first HARQ feedback codebook may be a first type ofHARQ feedback codebook; the second HARQ feedback codebook may be asecond type of HARQ feedback codebook; and the determining one of thefirst HARQ feedback codebook and the second HARQ feedback codebook maybe based on the first type and the second type. In an example, thedetermined HARQ feedback codebook may be the first HARQ feedback basedon a first priority of the first type being higher than a secondpriority of the second type. In an example, the first configurationparameters may comprise a first parameter indicating the first priority;and the second configuration parameters may comprise a second parameterindicating the second priority.

In an example embodiment, a wireless device may receive configurationparameters of a plurality of downlink semi-persistent schedulingconfigurations. The wireless device may receive a downlink controlinformation indicating release/deactivation of the plurality of downlinksemi-persistent scheduling configurations, wherein the plurality ofdownlink semi-persistent scheduling configurations may be associatedwith a plurality of HARQ feedback codebooks. The wireless device maydetermine a HARQ feedback codebook of the plurality of HARQ feedbackcodebooks based on one or more criteria. The wireless device maytransmit an acknowledgement based on the receiving the downlink controlinformation and based on the determined HARQ feedback codebook.

In an example, the configuration parameters may comprise one or moreparameters indicating one or more of the plurality of HARQ feedbackcodebooks. In an example, the configuration parameters may comprisefirst configuration parameters for a first downlink semi-persistentscheduling configuration of the plurality of downlink semi-persistentscheduling configurations; and the first configuration parameters maycomprise a first parameter indicating a HARQ feedback codebook of theplurality of HARQ feedback codebooks. In an example, the firstconfiguration parameters further comprise a periodicity parameter, anumber of HARQ processes, etc.

In an example, the wireless device may receive a first downlink controlinformation indicating: scheduling activation of a first downlinksemi-persistent scheduling configuration of the plurality of downlinksemi-persistent scheduling configurations; and a first HARQ feedbackcodebook. In an example, an RNTI associated with the first downlinkcontrol information may indicate the first HARQ feedback codebook. In anexample, the RNTI associated with the first downlink control informationmay indicate a first priority indicating the first HARQ feedbackcodebook. In an example, a value of a field of the first downlinkcontrol information may indicate the first HARQ feedback codebook. In anexample, a value of a field of the first downlink control informationmay indicate a first priority indicating the first HARQ feedbackcodebook. In an example, a search space/CORESET associated with thefirst downlink control information may indicate the first HARQ feedbackcodebook. In an example, a search space/CORESET associated with thefirst downlink control information may indicate a first priorityindicating the first HARQ feedback codebook. In an example, a firstformat associated with the first downlink control information mayindicate the first HARQ feedback codebook. In an example, a first formatassociated with the first downlink control information may indicate afirst priority indicating the first HARQ feedback codebook.

In an example, a HARQ feedback codebook, in the plurality of HARQfeedback codebooks, may be associated with a priority. In an example,the first HARQ feedback code book may be associated with atraffic/service type. In an example, the traffic/service type may beURLLC. In an example, the traffic/service type may be eMBB.

In an example, the determining the HARQ feedback codebook of theplurality of HARQ feedback codebooks may be based on a plurality ofpriorities associated with the plurality of HARQ feedback codebooks.

In an example, the determining the HARQ feedback codebook of theplurality of HARQ feedback codebooks may be based on a plurality oftraffic/service types associated with the plurality of HARQ feedbackcodebooks.

In an example, the determining the HARQ feedback codebook of theplurality of HARQ feedback codebooks may be based on a plurality oftypes associated with the plurality of HARQ feedback codebooks. In anexample, the determining the HARQ feedback codebook of the plurality ofHARQ feedback codebooks may be based on a plurality of prioritiesassociated with the plurality of types. In an example, the configurationparameters may comprise a plurality of parameters indicating theplurality of priorities associated with the plurality of types.

In an example, the determining the HARQ feedback codebook of theplurality of HARQ feedback codebooks may be based on a majority of theplurality of HARQ feedback codebooks being the determined HARQ feedbackcodebook.

In an example, the plurality of HARQ feedback codebooks may comprisezero or more of a first HARQ feedback codebook, corresponding to a firstpriority, and zero or more of a second HARQ feedback codebook,corresponding to a second priority, wherein the first priority may behigher than the second priority. In an example, the first HARQ feedbackcodebook may be for a first type of traffic/service and the second HARQfeedback codebook is for a second type of traffic/service. In anexample, the determined HARQ feedback codebook may be the first HARQfeedback codebook based on at least one of the plurality of HARQfeedback codebooks being the first HARQ feedback codebook.

In an example, the wireless device may determine the determined HARQfeedback codebook to be the first HARQ feedback codebook based on theplurality of HARQ feedback codebooks comprising an equal number of firstHARQ feedback codebooks and second HARQ feedback codebooks.

In an example, the determined HARQ feedback codebook may be apre-configured/configured HARQ feedback codebook. In an example, theconfiguration parameters (e.g., the one or more messages) may comprise aparameter indicating the determined HARQ feedback codebook.

In an example embodiment, a wireless device may receive configurationparameters of two downlink semi-persistent scheduling configurations.The wireless device may receive a downlink control informationindicating release/deactivation of the two downlink semi-persistentscheduling configurations. The wireless device may determine that twodownlink semi-persistent configurations correspond to different HARQfeedback codebooks. The wireless device may ignore the downlink controlinformation based on the determining.

In an example embodiment, a wireless device may receive configurationparameters of a plurality of downlink semi-persistent schedulingconfigurations. The wireless device may receive a downlink controlinformation indicating release/deactivation of the plurality of downlinksemi-persistent scheduling configurations, wherein the plurality ofdownlink semi-persistent scheduling configurations may be associatedwith a plurality of HARQ feedback codebooks. The wireless device maydetermine that: one or more first downlink semi-persistentconfigurations in the plurality of downlink semi-persistentconfigurations correspond to a first HARQ feedback codebook; and amajority of HARQ feedback codebooks in the plurality of HARQ feedbackcodebooks is the first HARQ feedback codebook. The wireless device mayrelease/deactivate the one or more first downlink semi-persistentscheduling configurations based on the receiving the downlink controlinformation. The wireless device may transmit an acknowledgement basedon the first HARQ feedback codebook.

In an example, the wireless device may not release/deactivate otherremaining downlink semi-persistent scheduling configurations in theplurality of downlink semi-persistent scheduling configurations.

In an example embodiment, a wireless device may receive configurationparameters of a plurality of downlink semi-persistent schedulingconfigurations. The wireless device may receive a downlink controlinformation indicating release/deactivation of one or more downlinksemi-persistent scheduling configurations, wherein: the one or moredownlink semi-persistent scheduling configurations are associated withone or more first HARQ feedback codebooks; and the downlink controlinformation indicates a second HARQ feedback codebook. The wirelessdevice may release/deactivate the one or more downlink semi-persistentscheduling configurations based on the receiving the downlink controlinformation. The wireless device may transmit an acknowledgement basedon the second HARQ feedback codebook and regardless of the one or morefirst HARQ feedback codebooks.

In an example embodiment, a wireless device may receive firstconfiguration parameters of a first downlink semi-persistent schedulingconfiguration and second configuration parameters of a second downlinksemi-persistent scheduling configuration. The wireless device mayreceive a downlink control information indicating release/deactivationof the first downlink semi-persistent scheduling configuration andrelease/deactivation of the second downlink semi-persistent schedulingconfiguration, wherein: the first downlink semi-persistent scheduling isassociated with a first HARQ feedback codebook; and the second downlinksemi-persistent scheduling is associated with a second HARQ feedbackcodebook. Based on the receiving the downlink control information: thewireless device may transmit a first acknowledgement based on the firstHARQ feedback codebook; and the wireless device may transmit a secondacknowledgement based on the second HARQ feedback codebook.

In an example embodiment, a wireless device may receive configurationparameters of a plurality of downlink semi-persistent schedulingconfigurations. The wireless device may receive a downlink controlinformation indicating release/deactivation of the plurality of downlinksemi-persistent scheduling configurations, wherein the plurality ofdownlink semi-persistent scheduling configurations are associated with aplurality of HARQ feedback codebooks. Based on the receiving thedownlink control information: the wireless device may transmit a firstacknowledgement using the first HARQ feedback codebook based on theplurality HARQ feedback codebook comprising the first HARQ feedbackcodebook; and the wireless device may transmit a second acknowledgementusing a second HARQ feedback codebook based on the plurality HARQfeedback codebooks comprising the second HARQ feedback codebook.

In an example, the first configuration parameters may comprise a firstparameter indicating a first HARQ feedback codebook. The secondconfiguration parameters comprise a second parameter indicating a secondHARQ feedback codebook.

In an example, the wireless device may receive a first downlink controlinformation indicating: scheduling activation of the first downlinksemi-persistent scheduling; and the first HARQ feedback codebook.

In an example, the wireless device may receive a second downlink controlinformation indicating: scheduling activation of the second downlinksemi-persistent scheduling; and the second HARQ feedback codebook.

In an example, the first downlink control information may indicate thefirst HARQ feedback codebook, wherein the HARQ feedback codebookindicated by the first downlink control information may overwrite a HARQfeedback codebook indicated by a first parameter of the firstconfiguration parameters.

In an example, the second downlink control information may indicate thesecond HARQ feedback codebook, wherein the HARQ feedback codebookindicated by the second downlink control information may overwrite aHARQ feedback codebook indicated by a second parameter of the secondconfiguration parameters.

In an example, the first HARQ feedback may be associated with a firstpriority. In an example, the first HARQ feedback code book may beassociated with a first traffic/service type.

In an example, the second HARQ feedback may be associated with a secondpriority. In an example, the second HARQ feedback code book may beassociated with a second traffic/service type.

For deactivation of a DL SPS configurations, the base station maytransmit a release/deactivation DCI indicating that the DL SPSconfiguration is deactivated. It is important for the wireless device toacknowledge the receipt of the release/deactivation DCI so that the basestation determines that the wireless device correctly received the DCIand that the wireless device deactivated resources corresponding to theDL SPS configurations. When a group of DL SPS configurations are jointlydeactivated/released by a deactivation/release DCI, existing wirelessdevice feedback solutions lead to inefficient DL SPS operation. There isa need to enhance the existing DL SPS deactivation/release mechanismswhen a group of DL SPS configurations are jointly released/deactivated.Example embodiments enhance the DL SPS deactivation/release mechanismswhen a group of DL SPS configurations are jointly released/deactivated.

In example embodiments as shown in FIG. 26 , FIG. 27 , FIG. 28 and FIG.29 , a wireless device may receive one or more messages comprisingconfiguration parameters of one or more cells. The one or more messagesmay comprise one or more radio resource control (RRC) messages. Theconfiguration parameters may comprise bandwidth part (BWP) configurationparameters of one or more BWPs of a cell of the one or more cells. Theconfiguration parameters may comprise first configuration parameters ofa first semi-persistent scheduling (SPS) configuration. The firstconfiguration parameters of the first SPS configuration may comprise afirst SPS configuration index and a first hybrid automatic repeatrequest (HARQ) codebook identifier. The first SPS configuration indexmay be used as an identifier of the first SPS configuration in aplurality of SPS configurations. The first HARQ codebook identifier mayindicate a first HARQ codebook that may be used by the wireless devicefor transmission of HARQ feedback (HARQ ACK/NACK) corresponding todownlink SPS transport blocks that are received via radio resourcesassociated with the first SPS configuration or may be used fortransmission of an acknowledgement (e.g., HARQ ACK) in response toreception of a release DCI indicating release/deactivation of the firstSPS configuration. The wireless device may construct the first HARQfeedback codebook and include in the first HARQ feedback codebook theHARQ feedback (HARQ ACK/NACK) corresponding to downlink SPS transportblocks that are received via radio resources associated with the firstSPS configuration or a HARQ ACK in response to reception of a releaseDCI indicating release/deactivation of the first SPS configuration. Thefirst configuration parameters of the first SPS configuration mayfurther comprise other SPS parameters such as a first periodicity (e.g.,in terms of number of symbols), first parameters for determiningtime/frequency resources associated with the first SPS configuration,etc. The configuration parameters may further comprise secondconfiguration parameters of a second SPS configuration. The secondconfiguration parameters of the second SPS configuration may comprise asecond SPS configuration index and a second hybrid automatic repeatrequest (HARQ) codebook identifier. The second SPS configuration indexmay be used as an identifier of the second SPS configuration in aplurality of SPS configurations. The second HARQ codebook identifier mayindicate a second HARQ codebook that may be used by the wireless devicefor transmission of HARQ feedback (HARQ ACK/NACK) corresponding todownlink SPS transport blocks that are received via radio resourcesassociated with the second SPS configuration or may be used fortransmission of an acknowledgement (e.g., HARQ ACK) in response toreception of a release DCI indicating release/deactivation of the secondSPS configuration. The wireless device may construct the second HARQfeedback codebook and include in the second HARQ feedback codebook theHARQ feedback (HARQ ACK/NACK) corresponding to downlink SPS transportblocks that are received via radio resources associated with the secondSPS configuration or a HARQ ACK in response to reception of a releaseDCI indicating release/deactivation of the second SPS configuration. Thesecond configuration parameters of the second SPS configuration mayfurther comprise other SPS parameters such as a second periodicity(e.g., in terms of number of symbols), second parameters for determiningtime/frequency resources associated with the second SPS configuration,etc. In an example, the first SPS configuration and the second SPSconfiguration may be configured for the BWP, in the one or more BWPs, ofthe cell in the one or more cells. In an example, a plurality of SPSconfigurations may be configured for the BWP of the cell and the firstSPS configuration index and the second SPS configuration index mayindicate, respectively, the first SPS configuration and the second SPSconfiguration in the plurality of SPS configurations configured for theBWP.

The configuration parameters may further comprise a third configurationparameter indicating a SPS deactivation state. The wireless device maybe configured with a SPS deactivation state list comprising a pluralityof SPS deactivation states (including the SPS deactivation stateindicated by the third configuration parameter) and each SPSdeactivation state, in the SPS deactivation state list, may beassociated with one or more SPS configuration indexes. The SPSdeactivation state may be used by wireless device to determine one ormore SPS configurations that may be jointly deactivated in response toreceiving a deactivation DCI indicating the deactivation state. The BWPconfiguration parameters of a downlink BWP may comprise the parameterindicating the deactivation state list for SPS configurations configuredon the downlink BWP.

The wireless device may receive a DCI comprising a plurality of fieldsincluding a HARQ process number (HPN) field, a new data indicator (NDI)field, a redundancy version (RV) field, etc. The DCI may be associatedwith an RNTI that may be used for activation/deactivation of a SPSconfiguration or a configured grant configuration and/or may be used forscheduling a retransmission of a SPS TB or a configured grant TB. TheRNTI may be a configured scheduling RNTI (CS-RNTI). The NDI field of theDCI may have a value of zero. Based on the DCI being associated with theCS-RNTI and the value of the NDI field being zero, the wireless devicemay perform a validation process to validate the DCI as a validactivation DCI or a valid release/deactivation DCI. The wireless devicemay determine that the DCI is a valid release/deactivation DCI based onthe validation process. The value of HARQ process number field of theDCI may indicate the deactivation state configured using the thirdconfiguration parameter. Based on the deactivation state beingassociated with the first SPS configuration and the second SPSconfiguration and based on the validation process indicating that theDCI is a valid deactivation/release DCI, the wireless device maydetermine to release/deactivate the first SPS configuration and thesecond SPS configuration. Based on the deactivation state beingassociated with the first SPS configuration and the second SPSconfiguration and based on the validation process indicating that theDCI is a valid deactivation/release DCI, the wireless device mayrelease/deactivate the first SPS configuration and the second SPSconfiguration. The first HARQ codebook identifier, indicated by thefirst SPS configurations, and the second HARQ codebook identifier,indicated by the second SPS configurations, may be the same. The firstHARQ codebook identifier, indicated by the first SPS configurations, andthe second HARQ codebook identifier, indicated by the second SPSconfigurations, may be the same in response to the deactivation statebeing associated with the first SPS configuration (first SPSconfiguration index) and the second SPS configuration (second SPSconfiguration index). The first HARQ codebook identifier, indicated bythe first SPS configurations, and the second HARQ codebook identifier,indicated by the second SPS configurations, may be the same in responseto the first SPS configuration (first SPS configuration index) and thesecond SPS configuration (second SPS configuration index) beingassociated with the same SPS deactivation state, e.g., in response tothe first configuration index and the second configuration index beingamong the plurality of configuration indexes associated with SPSdeactivation state. The wireless device may transmit an acknowledgement(e.g., HARQ ACK) in response to receiving the DCI. The wireless devicemay transmit the acknowledgement indicating the reception of the DCI(e.g., reception of the DCI that indicates SPS release of the first SPSconfiguration and the second SPS configuration). In example embodimentsas shown in FIG. 28 and FIG. 29 , the wireless device may transmit theacknowledgement based on the first HARQ codebook identifier being thesame as the second HARQ codebook identifier in response to the first SPSconfiguration index and the second SPS configuration index beingassociated with the same deactivation state. The wireless device maytransmit the acknowledgement based on the first HARQ codebook identifierbeing the same as the second HARQ codebook identifier in response to theDCI indicating joint deactivation/release of the first SPS configurationand the second SPS configuration.

In an example embodiment as shown in FIG. 30 , the wireless device mayreceive a DCI indicating release of a plurality of SPS configurations(e.g., the first SPS configuration and the second SPS configuration).The wireless device may transmit a single acknowledgement (e.g., asingle HARQ ACK) in response to receiving the DCI indicating release ofall of the plurality of the SPS configurations (e.g., both of the firstSPS configuration and the second SPS configuration). The singleacknowledgement may be for all of the plurality of SPS configurationsthat are indicated by the DCI to be released/deactivated.

In accordance with various exemplary embodiments in the presentdisclosure, a device (e.g., a wireless device, a base station and/oralike) may include one or more processors and may include memory thatmay store instructions. The instructions, when executed by the one ormore processors, cause the device to perform actions as illustrated inthe accompanying drawings and described in the specification. The orderof events or actions, as shown in a flow chart of this disclosure, mayoccur and/or may be performed in any logically coherent order. In someexamples, at least two of the events or actions shown may occur or maybe performed at least in part simultaneously and/or in parallel. In someexamples, one or more additional events or actions may occur or may beperformed prior to, after, or in between the events or actions shown inthe flow charts of the present disclosure.

FIG. 31 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 3110, a wirelessdevice may receive: first configuration parameters, of a firstsemi-persistent scheduling (SPS) configuration, comprising a firstconfiguration index and a first hybrid automatic repeat request (HARQ)codebook identifier; second configuration parameters, of a second SPSconfiguration, comprising a second configuration index and a second HARQcodebook identifier; and a third configuration parameter indicating adeactivation state associated with the first configuration index and thesecond configuration index. At 3120, the wireless device may receive adownlink control information comprising a HARQ process number field. Avalue of one or more bits of the HARQ process number field may indicatethe deactivation state. The first HARQ codebook identifier may be thesame as the second HARQ codebook identifier. At 3130, the wirelessdevice may transmit an acknowledgment indicating reception of thedownlink control information.

In an example embodiment, based on receiving the DCI at 3120, thewireless device may deactivate: first plurality of resources associatedwith the first SPS configuration; and second plurality of resourcesassociated with the second SPS configuration.

In an example embodiment, the DCI, received at 3120, may comprise aphysical downlink shared channel (PDSCH)-to-HARQ feedback timing filed.A value of the PDSCH-to-HARQ feedback timing field may indicate a timeduration between the downlink control information and theacknowledgement. In an example embodiment, the wireless device maydetermine a timing of the acknowledgement based on a first timing of thedownlink control information and the value of the PDSCH-to-HARQ feedbacktiming field.

In an example embodiment, the first HARQ codebook identifier mayindicate a first HARQ feedback codebook for transmission of anacknowledgement associated with releasing the first SPS configuration ora HARQ feedback for a transport block received via a resource associatedwith the first SPS configuration. The second HARQ codebook identifiermay indicate a second HARQ feedback codebook for transmission of anacknowledgement associated with releasing the second SPS configurationor a HARQ feedback for a transport block received via a resourceassociated with the second SPS configuration. The first HARQ feedbackcodebook may be the same as the second HARQ feedback codebook based onthe first HARQ codebook identifier being the same as the second HARQcodebook identifier.

In an example embodiment the deactivation state, indicated by the thirdconfiguration parameter received at 3110, may be associated with aplurality of configuration indexes comprising the first configurationindex and the second configuration index.

In an example embodiment, transmitting the acknowledgement at 3130 maybe in response to the downlink control information, received at 3120,indicating release of the first SPS configuration and the second SPSconfiguration.

In an example embodiment, the wireless device may further receive, at3110, a fourth configuration parameter indicating a configuredscheduling radio network temporary identifier, wherein the downlinkcontrol information, received at 3120, may be associated with theconfigured scheduling radio network temporary identifier.

In an example embodiment, the wireless device may further receive afirst activation downlink control information indicating activation of afirst plurality of resources associated with the first SPSconfiguration. The wireless device may further receive a secondactivation downlink control information indicating activation of asecond plurality if resources associated with the second SPSconfiguration.

In an example embodiment, the wireless device may further receive, at3110, fourth configuration parameters of a bandwidth part of a cell,wherein the first SPS configuration and the second SPS configuration maybe for the bandwidth part.

FIG. 32 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 3210, a wirelessdevice may receive: first semi-persistent scheduling (SPS) configurationparameters comprising a first hybrid automatic repeat request (HARQ)codebook identifier; and second SPS configuration parameters comprisinga second HARQ codebook identifier. At 3220, the wireless device mayreceive a downlink control information (DCI). A value of one or morebits of a HARQ process number field of the DCI may indicate the firstSPS configuration and the second SPS configuration. The first HARQcodebook identifier may be the same as the second HARQ codebookidentifier. At 3230, the wireless device may transmit an acknowledgmentindicating reception of the downlink control information.

In an example embodiment, the first SPS configuration parameters,received at 3210, may further comprise a first SPS configuration index.The second SPS configuration parameters, received at 3210, may furthercomprise a second SPS configuration index. The value of one or more bitsof the HARQ process number field of the DCI, received at 3220, mayindicate a deactivation state associated with the first SPSconfiguration index and the second SPS configuration index.

FIG. 33 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 3310, the wirelessdevice may receive: first configuration parameters, of a firstsemi-persistent scheduling (SPS) configuration, comprising a firstconfiguration index and a first hybrid automatic repeat request (HARQ)codebook identifier; second configuration parameters, of a second SPSconfiguration, comprising a second configuration index and a second HARQcodebook identifier; and a third configuration parameter indicating adeactivation state associated with the first configuration index and thesecond configuration index. At 3320, the wireless device may receive adownlink control information comprising a HARQ process number field. Avalue of one or more bits of the HARQ process number field may indicatethe deactivation state. At 3330, the wireless device may transmit, basedon the first HARQ codebook identifier being the same as the second HARQcodebook identifier, an acknowledgment indicating reception of thedownlink control information.

FIG. 34 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 3410, a wirelessdevice may receive: first semi-persistent scheduling (SPS) configurationparameters comprising a first hybrid automatic repeat request (HARQ)codebook identifier; and second SPS configuration parameters comprisinga second HARQ codebook identifier. At 3420, the wireless device mayreceive a downlink control information comprising a HARQ process numberfield. A value of one or more bits of the HARQ process number field mayindicate the first SPS configuration and the second SPS configuration.At 3430, the wireless device may transmit, based on the first HARQcodebook identifier being the same as the second HARQ codebookidentifier, an acknowledgment indicating reception of the downlinkcontrol information.

In an example embodiment, the first SPS configuration parameters,received at 3410, may further comprise a first SPS configuration index.The second SPS configuration parameters, received at 3410, may furthercomprise a second SPS configuration index. The value of one or more bitsof the HARQ process number field of the DCI, received at 3420, mayindicate a deactivation state associated with the first SPSconfiguration index and the second SPS configuration index.

In an example embodiment, a wireless device may receive: firstconfiguration parameters of a first semi-persistent scheduling (SPS)configuration; and second configuration parameters of a second SPSconfiguration. The wireless device may receive a downlink controlinformation comprising a HARQ process number field, wherein: a value ofone or more bits of the HARQ process number field indicates the firstSPS configuration and the second SPS configuration; and the downlinkcontrol information indicates releasing the first SPS configuration andthe second SPS configuration. The wireless device may transmit a singleacknowledgment in response to reception of the downlink controlinformation indicating release of both of the first SPS configurationand the second SPS configuration.

In an example embodiment, the first SPS configuration parameters maycomprise a first SPS configuration index. The second SPS configurationparameters may comprise a second SPS configuration index. The value ofthe one or more bits of the HARQ process number field of the downlinkcontrol information may indicate a deactivation state associated withthe first SPS configuration index and the second SPS configurationindex.

FIG. 35 shows an example flow diagram in accordance with several ofvarious embodiments of the present disclosure. At 3510, a wirelessdevice may receive first configuration parameters of a firstsemi-persistent scheduling (SPS) configuration; and second configurationparameters of a second SPS configuration. At 3520, the wireless devicemay receive a downlink control information indicating releasing thefirst SPS configuration and the second SPS configuration. At 3530, thewireless device may transmit a single acknowledgment in response toreception of the downlink control information indicating release of bothof the first SPS configuration and the second SPS configuration.

In an example embodiment, the first SPS configuration parameters,received at 3510, may comprise a first SPS configuration index. Thesecond SPS configuration parameters, received at 3510, may comprise asecond SPS configuration index. A value of one or more bits of the HARQprocess number field of the DCI, received at 3520, may indicate adeactivation state associated with the first SPS configuration index andthe second SPS configuration index.

Various exemplary embodiments of the disclosed technology are presentedas example implementations and/or practices of the disclosed technology.The exemplary embodiments disclosed herein are not intended to limit thescope. Persons of ordinary skill in the art will appreciate that variouschanges can be made to the disclosed embodiments without departure fromthe scope. After studying the exemplary embodiments of the disclosedtechnology, alternative aspects, features and/or embodiments will becomeapparent to one of ordinary skill in the art. Without departing from thescope, various elements or features from the exemplary embodiments maybe combined to create additional embodiments. The exemplary embodimentsare described with reference to the drawings. The figures and theflowcharts that demonstrate the benefits and/or functions of variousaspects of the disclosed technology are presented for illustrationpurposes only. The disclosed technology can be flexibly configuredand/or reconfigured such that one or more elements of the disclosedembodiments may be employed in alternative ways. For example, an elementmay be optionally used in some embodiments or the order of actionslisted in a flowchart may be changed without departure from the scope.

An example embodiment of the disclosed technology may be configured tobe performed when deemed necessary, for example, based on one or moreconditions in a wireless device, a base station, a radio and/or corenetwork configuration, a combination thereof and/or alike. For example,an example embodiment may be performed when the one or more conditionsare met. Example one or more conditions may be one or moreconfigurations of the wireless device and/or base station, traffic loadand/or type, service type, battery power, a combination of thereofand/or alike. In some scenarios and based on the one or more conditions,one or more features of an example embodiment may be implementedselectively.

In this disclosure, the articles “a” and “an” used before a group of oneor more words are to be understood as “at least one” or “one or more” ofwhat the group of the one or more words indicate. The use of the term“may” before a phrase is to be understood as indicating that the phraseis an example of one of a plurality of useful alternatives that may beemployed in an embodiment in this disclosure.

In this disclosure, an element may be described using the terms“comprises”, “includes” or “consists of” in combination with a list ofone or more components. Using the terms “comprises” or “includes”indicates that the one or more components are not an exhaustive list forthe description of the element and do not exclude components other thanthe one or more components. Using the term “consists of” indicates thatthe one or more components is a complete list for description of theelement. In this disclosure, the term “based on” is intended to mean“based at least in part on”. The term “based on” is not intended to mean“based only on”. In this disclosure, the term “and/or” used in a list ofelements indicates any possible combination of the listed elements. Forexample, “X, Y, and/or Z” indicates X; Y; Z; X and Y; X and Z; Y and Z;or X, Y, and Z.

Some elements in this disclosure may be described by using the term“may” in combination with a plurality of features. For brevity and easeof description, this disclosure may not include all possiblepermutations of the plurality of features. By using the term “may” incombination with the plurality of features, it is to be understood thatall permutations of the plurality of features are being disclosed. Forexample, by using the term “may” for description of an element with fourpossible features, the element is being described for all fifteenpermutations of the four possible features. The fifteen permutationsinclude one permutation with all four possible features, fourpermutations with any three features of the four possible features, sixpermutations with any two features of the four possible features andfour permutations with any one feature of the four possible features.

Although mathematically a set may be an empty set, the term set used inthis disclosure is a nonempty set. Set B is a subset of set A if everyelement of set B is in set A. Although mathematically a set has an emptysubset, a subset of a set is to be interpreted as a non-empty subset inthis disclosure. For example, for set A={subcarrier1, subcarrier2}, thesubsets are {subcarrier1}, {subcarrier2} and {subcarrier1, subcarrier2}.

In this disclosure, the phrase “based on” may be used equally with“based at least on” and what follows “based on” or “based at least on”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure. The phrase “in response to”may be used equally with “in response at least to” and what follows “inresponse to” or “in response at least to” indicates an example of one ofplurality of useful alternatives that may be used in an embodiment inthis disclosure. The phrase “depending on” may be used equally with“depending at least on” and what follows “depending on” or “depending atleast on” indicates an example of one of plurality of usefulalternatives that may be used in an embodiment in this disclosure. Thephrases “employing” and “using” and “employing at least” and “using atleast” may be used equally in this in this disclosure and what follows“employing” or “using” or “employing at least” or “using at least”indicates an example of one of plurality of useful alternatives that maybe used in an embodiment in this disclosure.

The example embodiments disclosed in this disclosure may be implementedusing a modular architecture comprising a plurality of modules. A modulemay be defined in terms of one or more functions and may be connected toone or more other elements and/or modules. A module may be implementedin hardware, software, firmware, one or more biological elements (e.g.,an organic computing device and/or a neurocomputer) and/or a combinationthereof and/or alike. Example implementations of a module may be assoftware code configured to be executed by hardware and/or a modelingand simulation program that may be coupled with hardware. In an example,a module may be implemented using general-purpose or special-purposeprocessors, digital signal processors (DSPs), microprocessors,microcontrollers, application-specific integrated circuits (ASICs),programmable logic devices (PLDs) and/or alike. The hardware may beprogrammed using machine language, assembly language, high-levellanguage (e.g., Python, FORTRAN, C, C++ or the like) and/or alike. In anexample, the function of a module may be achieved by using a combinationof the mentioned implementation methods.

What is claimed is:
 1. A method comprising: transmitting, by a basestation, one or more radio resource control (RRC) messages comprising: afirst configuration parameter, of a first semi-persistent scheduling(SPS) configuration, indicating a first hybrid automatic repeat request(HARQ) codebook identifier; a second configuration parameter, of asecond SPS configuration, indicating a second HARQ codebook identifier,wherein the second HARQ codebook identifier is the same as the firstHARQ codebook identifier; and a third configuration parameter indicatinga state that is mapped to the first SPS configuration and the second SPSconfiguration; transmitting a downlink control information (DCI),wherein: a value of one or more bits of a HARQ process number field ofthe DCI indicates the state; and the DCI indicates deactivation of thefirst SPS configuration and the second SPS configuration; and receivingan acknowledgement.
 2. The method of claim 1, wherein the deactivationof the first SPS configuration and the second SPS configurationcomprises deactivation of: a first plurality of resources associatedwith the first SPS configuration; and a second plurality of resourcesassociated with the second SPS configuration.
 3. The method of claim 1,wherein: the DCI comprises a physical downlink shared channel(PDSCH)-to-HARQ feedback timing field; and a value of the PDSCH-to-HARQfeedback timing field indicates a time duration between the DCI and theacknowledgement.
 4. The method of claim 3, wherein a timing of theacknowledgement is based on a first timing of the DCI and the value ofthe PDSCH-to-HARQ feedback timing field.
 5. The method of claim 1,wherein: the first HARQ codebook identifier indicates a first HARQfeedback codebook for transmission of an acknowledgement associated withreleasing the first SPS configuration or a HARQ feedback for a transportblock received via a resource associated with the first SPSconfiguration; the second HARQ codebook identifier indicates a secondHARQ feedback codebook for transmission of an acknowledgement associatedwith releasing the second SPS configuration or a HARQ feedback for atransport block received via a resource associated with the second SPSconfiguration; and the first HARQ feedback codebook is the same as thesecond HARQ feedback codebook based on the first HARQ codebookidentifier being the same as the second HARQ codebook identifier.
 6. Themethod of claim 1, wherein the state is associated with a plurality ofconfiguration indexes comprising a first configuration index, of thefirst SPS configuration, and a second configuration index of the secondSPS configuration.
 7. The method of claim 1, wherein the receiving theacknowledgement is in response to the DCI indicating release of thefirst SPS configuration and the second SPS configuration.
 8. The methodof claim 1, wherein the one or more RRC messages further comprise afourth configuration parameter indicating a configured scheduling radionetwork temporary identifier, wherein the DCI is associated with theconfigured scheduling radio network temporary identifier.
 9. The methodof claim 1, further comprising: transmitting a first activation DCIindicating activation of a first plurality of resources associated withthe first SPS configuration; and transmitting a second activation DCIindicating activation of a second plurality of resources associated withthe second SPS configuration.
 10. The method of claim 1, wherein the oneor more RRC messages further comprise fourth configuration parameters ofa bandwidth part of a cell, wherein the first SPS configuration and thesecond SPS configuration are for the bandwidth part.
 11. A base stationcomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the basestation to: transmit one or more radio resource control (RRC) messagescomprising: a first configuration parameter, of a first semi-persistentscheduling (SPS) configuration, indicating a first hybrid automaticrepeat request (HARQ) codebook identifier; a second configurationparameter, of a second SPS configuration, indicating a second HARQcodebook identifier, wherein the second HARQ codebook identifier is thesame as the first HARQ codebook identifier; and a third configurationparameter indicating a state that is mapped to the first SPSconfiguration and the second SPS configuration; transmit a downlinkcontrol information (DCI), wherein: a value of one or more bits of aHARQ process number field of the DCI indicates the state; and the DCIindicates deactivation of the first SPS configuration and the second SPSconfiguration; and receive an acknowledgement.
 12. The base station 11,wherein the deactivation of the first SPS configuration and the secondSPS configuration comprises deactivation of: a first plurality ofresources associated with the first SPS configuration; and a secondplurality of resources associated with the second SPS configuration. 13.The base station of claim 11, wherein: the DCI comprises a physicaldownlink shared channel (PDSCH)-to-HARQ feedback timing field; and avalue of the PDSCH-to-HARQ feedback timing field indicates a timeduration between the DCI and the acknowledgement.
 14. The base stationof claim 13, wherein a timing of the acknowledgement is based on a firsttiming of the DCI and the value of the PDSCH-to-HARQ feedback timingfield.
 15. The base station of claim 11, wherein: the first HARQcodebook identifier indicates a first HARQ feedback codebook fortransmission of an acknowledgement associated with releasing the firstSPS configuration or a HARQ feedback for a transport block received viaa resource associated with the first SPS configuration; the second HARQcodebook identifier indicates a second HARQ feedback codebook fortransmission of an acknowledgement associated with releasing the secondSPS configuration or a HARQ feedback for a transport block received viaa resource associated with the second SPS configuration; and the firstHARQ feedback codebook is the same as the second HARQ feedback codebookbased on the first HARQ codebook identifier being the same as the secondHARQ codebook identifier.
 16. The base station of claim 11, wherein thestate is associated with a plurality of configuration indexes comprisinga first configuration index, of the first SPS configuration, and asecond configuration index of the second SPS configuration.
 17. The basestation of claim 11, wherein receiving the acknowledgement is inresponse to the DCI indicating release of the first SPS configurationand the second SPS configuration.
 18. The base station of claim 11,wherein the one or more RRC messages further comprise a fourthconfiguration parameter indicating a configured scheduling radio networktemporary identifier, wherein the DCI is associated with the configuredscheduling radio network temporary identifier.
 19. The base station ofclaim 11, wherein the instructions, when executed by the one or moreprocessors, further cause the base station to: transmit a firstactivation DCI indicating activation of a first plurality of resourcesassociated with the first SPS configuration; and transmit a secondactivation DCI indicating activation of a second plurality of resourcesassociated with the second SPS configuration.
 20. The base station ofclaim 11, wherein the one or more RRC messages further comprise fourthconfiguration parameters of a bandwidth part of a cell, wherein thefirst SPS configuration and the second SPS configuration are for thebandwidth part.